https://gcc.gnu.org/bugzilla/show_bug.cgi?id=94646
Bug ID: 94646
Summary: [arm] invalid codegen for conversion from 64-bit int
to double hardfloat
Product: gcc
Version: unknown
Status: UNCONFIRMED
Severity:
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=94645
--- Comment #1 from Avi Kivity ---
Created attachment 48304
--> https://gcc.gnu.org/bugzilla/attachment.cgi?id=48304=edit
reduced test case (after preprocessing)
This is what the compiler spat out after it failed to compile the
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=94645
Bug ID: 94645
Summary: incorrect concecpt evaluation with decltype, plus
internal erropr
Product: gcc
Version: 10.0
Status: UNCONFIRMED
Severity: normal
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=94644
Bug ID: 94644
Summary: Wrong is_nothrow_move_constructible result if used in
a template first
Product: gcc
Version: unknown
Status: UNCONFIRMED
Severity:
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=94255
Marek Polacek changed:
What|Removed |Added
Status|NEW |ASSIGNED
Assignee|unassigned
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=94592
Marek Polacek changed:
What|Removed |Added
Keywords||patch
--- Comment #8 from Marek Polacek
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=88601
--- Comment #4 from Andrew Pinski ---
(In reply to Jeff Muizelaar from comment #3)
> As heads up, we're also starting to use __builtin_shufflevector in Firefox:
> https://searchfox.org/mozilla-central/source/gfx/wr/swgl/src/vector_type.h
>
> We
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=94643
Andrew Pinski changed:
What|Removed |Added
Ever confirmed|0 |1
Keywords|
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=61577
--- Comment #206 from dave.anglin at bell dot net ---
Does adding the linker option "-Wl,-O" help to reduce the size of cc1 and
cc1plus?
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=94643
Bug ID: 94643
Summary: [x86_64] gratuitous sign extension of nonnegative
value from 32 to 64 bits
Product: gcc
Version: unknown
Status: UNCONFIRMED
Severity:
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=88601
Jeff Muizelaar changed:
What|Removed |Added
CC||jmuizelaar at mozilla dot com
---
On Fri, Apr 17, 2020, 10:59 PM kamlesh kumar
wrote:
> Fixes all this.
> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=92156
> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=91630
> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=90415
>
> On Fri, Apr 17, 2020 at 10:45 PM kamlesh kumar
> wrote:
> >
>
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=94231
Marek Polacek changed:
What|Removed |Added
CC||mpolacek at gcc dot gnu.org
From: Douglas Rupp
Hello,
(submitting this on behalf of Doug Rupp, one of my colleagues)
We're getting an error when running this test on PowerPC VxWorks 7,
due to an unexpected warning:
| Excess errors:
| cc1: warning: '-mvsx' and '-mno-altivec' are incompatible
The warning comes
Some more C++20 changes from P1614R2, "The Mothership has Landed".
* include/std/chrono (duration, time_point): Define operator<=> and
remove redundant operator!= for C++20.
* testsuite/20_util/duration/comparison_operators/three_way.cc: New
test.
*
In C++20 the rebind and const_reference members of std::allocator are
gone, so this testsuite utility stopped working, causing
ext/pb_ds/regression/priority_queue_rand_debug.cc to FAIL.
* testsuite/util/native_type/native_priority_queue.hpp: Use
allocator_traits to rebind
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=94550
Marek Polacek changed:
What|Removed |Added
CC||mpolacek at gcc dot gnu.org
Some more C++20 changes from P1614R2, "The Mothership has Landed".
This implements <=> for sequence containers (and the __normal_iterator
and _Pointer_adapter class templates).
* include/bits/forward_list.h (forward_list): Define operator<=> and
remove redundant comparison
Snapshot gcc-8-20200417 is now available on
https://gcc.gnu.org/pub/gcc/snapshots/8-20200417/
and on various mirrors, see http://gcc.gnu.org/mirrors.html for details.
This snapshot has been generated from the GCC 8 git branch
with the following options: git://gcc.gnu.org/git/gcc.git branch
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=94417
--- Comment #8 from H.J. Lu ---
Fixed for GCC 10, GCC 9.4 and GCC 8.5.
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=94417
--- Comment #7 from CVS Commits ---
The releases/gcc-8 branch has been updated by H.J. Lu :
https://gcc.gnu.org/g:99ddb11c0840f68466a14fd583dd4d3a558d4961
commit r8-10186-g99ddb11c0840f68466a14fd583dd4d3a558d4961
Author: H.J. Lu
Date: Fri
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=89355
--- Comment #10 from CVS Commits ---
The releases/gcc-8 branch has been updated by H.J. Lu :
https://gcc.gnu.org/g:99ddb11c0840f68466a14fd583dd4d3a558d4961
commit r8-10186-g99ddb11c0840f68466a14fd583dd4d3a558d4961
Author: H.J. Lu
Date: Fri
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=94622
--- Comment #1 from acsawdey at gcc dot gnu.org ---
Compiling with -dap we see:
sync # 7[c=12 l=4] *hwsync
plq 8,.LANCHOR0@pcrel# 8[c=8 l=12] load_quadpti
mr 10,9 # 9[c=4
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=94417
--- Comment #6 from CVS Commits ---
The releases/gcc-9 branch has been updated by H.J. Lu :
https://gcc.gnu.org/g:4a745938b56da04ed01055d5bcb520dc1c760414
commit r9-8508-g4a745938b56da04ed01055d5bcb520dc1c760414
Author: H.J. Lu
Date: Fri
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=89355
--- Comment #9 from CVS Commits ---
The releases/gcc-9 branch has been updated by H.J. Lu :
https://gcc.gnu.org/g:4a745938b56da04ed01055d5bcb520dc1c760414
commit r9-8508-g4a745938b56da04ed01055d5bcb520dc1c760414
Author: H.J. Lu
Date: Fri
On Thu, 16 Apr 2020, David Malcolm wrote:
> Validates. The wording could probably use some work.
I did not really spot anything, and rather found your writing very
clear.
> OK to push to the website repo?
Yes, thank you.
> +https://cwe.mitre.org/;>CWE weakness identifiers, which
Here you
On Thu, 2020-04-16 at 19:15 -0400, David Malcolm via Gcc-patches wrote:
> Validates. The wording could probably use some work.
>
> OK to push to the website repo?
OK. As are any small updates if you wanted to twiddle the wording.
jeff
>
On Fri, 2020-04-17 at 08:18 -0700, H.J. Lu wrote:
> On Wed, Apr 8, 2020 at 9:41 AM Jeff Law wrote:
> > On Wed, 2020-04-08 at 09:23 -0700, H.J. Lu wrote:
> > > On Wed, Apr 8, 2020 at 9:16 AM Jeff Law wrote:
> > > > On Tue, 2020-03-31 at 08:11 -0700, H.J. Lu via Gcc-patches wrote:
> > > > > Since
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=94629
Martin Sebor changed:
What|Removed |Added
CC||msebor at gcc dot gnu.org
--- Comment
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=90983
Martin Sebor changed:
What|Removed |Added
Assignee|unassigned at gcc dot gnu.org |msebor at gcc dot
gnu.org
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=94642
Bug ID: 94642
Summary: missing -Wformat-overflow on %f with excessive
precision
Product: gcc
Version: 10.0
Status: UNCONFIRMED
Severity: normal
This isn't precisely the same issue that we were originally tracking with 90275,
but it's closely related and we might as well stuff it in the same bucket.
This time instead of having a NOP copy insn that we can completely ignore and
ultimately remove, we have a NOP set within a multi-set
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=90275
--- Comment #22 from CVS Commits ---
The master branch has been updated by Jeff Law :
https://gcc.gnu.org/g:3737ccc424c56a2cecff202dd79f88d28850eeb2
commit r10-7781-g3737ccc424c56a2cecff202dd79f88d28850eeb2
Author: Jeff Law
Date: Fri Apr 17
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=94550
Daniel Krügler changed:
What|Removed |Added
CC||daniel.kruegler@googlemail.
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=94641
Bug ID: 94641
Summary: -Wpadded -fsanitize=undefined together cause warning
on main()
Product: gcc
Version: 9.3.0
Status: UNCONFIRMED
Severity: normal
On 4/17/20 12:19 AM, Jason Merrill wrote:
On 4/15/20 1:30 PM, Martin Sebor wrote:
On 4/13/20 8:43 PM, Jason Merrill wrote:
On 4/12/20 5:49 PM, Martin Sebor wrote:
On 4/10/20 8:52 AM, Jason Merrill wrote:
On 4/9/20 4:23 PM, Martin Sebor wrote:
On 4/9/20 1:32 PM, Jason Merrill wrote:
On
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=94631
--- Comment #8 from Rich Felker ---
OK, I think it's in 6.3.1.1 Boolean, characters, and integers, ¶2, but somewhat
poorly worded:
"The following may be used in an expression wherever an int or unsigned int may
be used:
- An object or
On Fri, Apr 17, 2020 at 08:53:08AM +0200, Richard Biener wrote:
> On Thu, Apr 16, 2020 at 7:46 PM Segher Boessenkool
> wrote:
> >
> > On Thu, Apr 16, 2020 at 10:33:45AM +0200, Richard Biener wrote:
> > > On Wed, Apr 15, 2020 at 11:23 PM Segher Boessenkool
> > > > On a general note, we shouldn't
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=94631
--- Comment #7 from Rich Felker ---
Can you provide a citation for that?
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=94631
--- Comment #6 from joseph at codesourcery dot com ---
On Fri, 17 Apr 2020, bugdal at aerifal dot cx wrote:
> No, GCC's treatment also seems to mess up bitfields smaller than int and fully
> governed by the standard (no implementation-defined
As an extension (there should be a CWG about this though), we support
braced-init-list as a template argument, but convert_nontype_argument
had trouble digesting them. We ICEd because of the double coercion we
perform for template arguments: convert_nontype_argument called from
On Fri, Apr 17, 2020 at 10:33 AM Thomas Koenig wrote:
>
> Hi Fritz,
>
> > First, it appears if simplify_bound_dim returns _bad_expr (and a
> > div/0 occurs) then this code will free _bad_expr. I'm not sure
> > whether or not that can actually occur, but it is certainly incorrect,
> > since
Hi
Over at RTEMS, we have had a report that this very old code has quit
compiling:
#ifdef __SSE__
#define _CPU_Context_restore_fp(fp_context_pp) \
do { \
__asm__ __volatile__( \
"fldcw %0" \
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=93146
Andrew Paprocki changed:
What|Removed |Added
CC||andrew at ishiboo dot com
--- Comment
On 4/17/20 1:55 PM, Szabolcs Nagy wrote:
The 04/17/2020 12:50, Jason Merrill wrote:
On 4/17/20 6:08 AM, Kyrylo Tkachov wrote:
Hi Szabolcs,
-Original Message-
From: Szabolcs Nagy
Sent: 09 April 2020 15:20
To: gcc-patches@gcc.gnu.org
Cc: Richard Earnshaw ; Richard Sandiford
; Kyrylo
On 4/17/20 1:35 PM, Patrick Palka wrote:
In the testcase below, during specialization of c::d, we build two
identical specializations of the parameter type b -- one when
substituting into c::d's TYPE_ARG_TYPES and another when substituting into
c::d's DECL_ARGUMENTS.
We don't reuse the first
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=94439
--- Comment #6 from Jeffrey A. Law ---
And has likely been broken since the introduction of VTA if I'm reading the
code correctly.
On 4/17/20 11:48 AM, Alexandre Oliva wrote:
On Apr 9, 2020, Alexandre Oliva wrote:
Some target C libraries that aren't recognized as freestanding don't
have filesystem support, so calling tmpnam, fopen/open and
remove/unlink fails to link.
This patch introduces a tmpnam effective target
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=94439
Jeffrey A. Law changed:
What|Removed |Added
Assignee|unassigned at gcc dot gnu.org |law at redhat dot com
---
On 4/17/20 9:40 AM, Patrick Palka wrote:
When updating an auto return type of an abbreviated function template in
splice_late_return_type, we should also propagate PLACEHOLDER_TYPE_CONSTRAINTS
(and cv-qualifiers) of the original auto node.
Bootstrapped and regtested on x86_64-pc-linux-gnu, does
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=94635
Tobias Burnus changed:
What|Removed |Added
Status|ASSIGNED|RESOLVED
Resolution|---
The vsel instruction is a bit-wise select instruction. Using an
IF_THEN_ELSE to express it in RTL is wrong and leads to wrong code being
generated in the combine pass.
With the patch the pattern is written using bit operations. However,
I've just noticed that the manual still demands a fixed
Grillautomat mit kostenloser Beklebung
Besuchen Sie hier die
[Webversion](https://amxe.net/5ci6gq4n-dtlrq76a-3tasn6h2-1cgh).
Jetzt Grillfleischautomaten kaufen
==
Unsere Food-Box 24/7
Immer mehr Verbraucher sind auf der Suche nach
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=51513
Peter Bergner changed:
What|Removed |Added
Status|CLOSED |REOPENED
Resolution|FIXED
On Apr 9, 2020, Alexandre Oliva wrote:
> Some target C libraries that aren't recognized as freestanding don't
> have filesystem support, so calling tmpnam, fopen/open and
> remove/unlink fails to link.
> This patch introduces a tmpnam effective target to the testsuite, and
> requires it in the
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=94439
Jeffrey A. Law changed:
What|Removed |Added
CC||law at redhat dot com
--- Comment #4
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=88754
Patrick Palka changed:
What|Removed |Added
Summary|[8/9/10 Regression] |[8/9 Regression]
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=94483
Patrick Palka changed:
What|Removed |Added
Summary|[9/10 Regression] ICE: tree |[9 Regression] ICE: tree
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=88754
--- Comment #5 from CVS Commits ---
The master branch has been updated by Patrick Palka :
https://gcc.gnu.org/g:3f5af3f71195b7f1ebe32bd0d695b59904fff778
commit r10-7779-g3f5af3f71195b7f1ebe32bd0d695b59904fff778
Author: Patrick Palka
Date:
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=94483
--- Comment #3 from CVS Commits ---
The master branch has been updated by Patrick Palka :
https://gcc.gnu.org/g:a28edad3da5c59f09565d3d42e20be1a924986c4
commit r10-7780-ga28edad3da5c59f09565d3d42e20be1a924986c4
Author: Patrick Palka
Date:
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=94623
--- Comment #2 from David Binderman ---
Host and target are the same: x86_64-pc-linux-gnu
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=94637
Jakub Jelinek changed:
What|Removed |Added
CC||jakub at gcc dot gnu.org
--- Comment #5
The 04/17/2020 12:50, Jason Merrill wrote:
> On 4/17/20 6:08 AM, Kyrylo Tkachov wrote:
> > Hi Szabolcs,
> >
> > > -Original Message-
> > > From: Szabolcs Nagy
> > > Sent: 09 April 2020 15:20
> > > To: gcc-patches@gcc.gnu.org
> > > Cc: Richard Earnshaw ; Richard Sandiford
> > > ; Kyrylo
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=94090
Thomas Koenig changed:
What|Removed |Added
Resolution|--- |FIXED
Status|ASSIGNED
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=94090
--- Comment #4 from CVS Commits ---
The master branch has been updated by Thomas Kथà¤nig :
https://gcc.gnu.org/g:2298af0800b292f028298c1eaec42fd3033c4b9b
commit r10-7778-g2298af0800b292f028298c1eaec42fd3033c4b9b
Author: Thomas König
Date:
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=94106
Jeffrey A. Law changed:
What|Removed |Added
CC||law at redhat dot com
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=94637
Jeffrey A. Law changed:
What|Removed |Added
CC||law at redhat dot com
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=90392
Jeffrey A. Law changed:
What|Removed |Added
Status|WAITING |NEW
Summary|[8/9/10
In the testcase below, during specialization of c::d, we build two
identical specializations of the parameter type b -- one when
substituting into c::d's TYPE_ARG_TYPES and another when substituting into
c::d's DECL_ARGUMENTS.
We don't reuse the first specialization the second time around as a
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=90983
--- Comment #5 from Torsten Robitzki ---
(In reply to Martin Sebor from comment #4)
> Using a very large -Wstack-usage argument should effectively disable the
> warning. E.g., -Wstack-usage=4EiB or -Wstack-usage=$(getconf ULONG_MAX).
Hi,
This is a PING for an old patch proposed by H. J. Lu on Oct, 2018:
https://gcc.gnu.org/legacy-ml/gcc-patches/2018-10/msg02079.html
This is the first patch of the total 3 patches set, which provides the
following new feature:
-mzero-caller-saved-regs=[skip|used-gpr|all-gpr|used|all]
Hi,
This is the 2nd patch of the total 3 patches set for providing the new feature
-mzero-caller-saved-regs for linux kernel security improvement.
This patch is for resolving the new regressions triggered by the first patch.
This patch is to Add ix86_any_return_p to check simple_return in a
Hi,
This is the 3rd patch of the total 3 patches set for providing the new feature
-mzero-caller-saved-regs for linux kernel security improvement.
This patch is to
Update gcc.target/i386/ret-thunk-2[234].c
Qing
0003-Update-gcc.target-i386-ret-thunk-2-234-.c.patch
Description: Binary data
Fixes all this.
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=92156
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=91630
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=90415
On Fri, Apr 17, 2020 at 10:45 PM kamlesh kumar wrote:
>
> This patch corrects the requirement of 4,5 and 6th constructor
> As
This patch corrects the requirement of 4,5 and 6th constructor
As per https://en.cppreference.com/w/cpp/utility/any/any.
ChangeLog:
2020-04-17 Kamlesh Kumar
PR libstdc++/92156
* include/std/any (ans::any(_ValueType &&):: Remove
is_constructible.
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=94623
--- Comment #1 from Iain Buclaw ---
Needs more host/target information.
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=94635
--- Comment #2 from CVS Commits ---
The master branch has been updated by Tobias Burnus :
https://gcc.gnu.org/g:af557050fd011a03d21dc26b31959033061a0443
commit r10--gaf557050fd011a03d21dc26b31959033061a0443
Author: Tobias Burnus
Date:
Hi Andre,
the patch series passed bootstrap and check with no new fails on Graviton2
aarch64-linux.
Thanks,
Sebastian
On 4/16/20, 12:24 PM, "Pop, Sebastian" wrote:
Thanks Andre for the back-port to gcc-8. Overall the patches look good to
me.
Could you please move the patch
On Fri, Apr 17, 2020 at 12:45:37PM -0400, Jason Merrill via Gcc-patches wrote:
> On 4/16/20 7:33 PM, Patrick Palka wrote:
> > In the testcase for this PR, we try to parse the statement
> >
> >A(value<0>());
> >
> > first tentatively as a declaration (with a parenthesized declarator), and
>
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=90983
--- Comment #4 from Martin Sebor ---
Using a very large -Wstack-usage argument should effectively disable the
warning. E.g., -Wstack-usage=4EiB or -Wstack-usage=$(getconf ULONG_MAX).
On 4/17/20 6:08 AM, Kyrylo Tkachov wrote:
Hi Szabolcs,
-Original Message-
From: Szabolcs Nagy
Sent: 09 April 2020 15:20
To: gcc-patches@gcc.gnu.org
Cc: Richard Earnshaw ; Richard Sandiford
; Kyrylo Tkachov
Subject: [PATCH] aarch64: Fix .cfi_window_save with pac-ret [PR94515]
On
On 4/16/20 7:33 PM, Patrick Palka wrote:
In the testcase for this PR, we try to parse the statement
A(value<0>());
first tentatively as a declaration (with a parenthesized declarator), and during
this tentative parse we end up issuing a hard error from
cp_parser_check_template_parameters
On 4/16/20 1:53 PM, Patrick Palka wrote:
In this PR (which I think is misclassified as ice-on-invalid instead of
ice-on-valid), we're ICEing on a use of an 'int... a' template parameter pack as
part of the variadic lambda init-capture [...z=a].
The unexpected thing about this variadic
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=94637
--- Comment #4 from Andrew Pinski ---
The change needs to happen inside c_parser_objc_selector_arg.
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=94637
Andrew Pinski changed:
What|Removed |Added
Ever confirmed|0 |1
Keywords|
On Fri, Apr 17, 2020 at 05:57:06PM +0200, Tobias Burnus wrote:
> --- a/gcc/gimplify.c
> +++ b/gcc/gimplify.c
> @@ -8785,11 +8785,15 @@ gimplify_scan_omp_clauses (tree *list_p, gimple_seq
> *pre_p,
>'exit data' - and in particular for 'delete:' - having an 'alloc:'
>does
On Thu, Apr 16, 2020 at 08:21:40PM -0500, Segher Boessenkool wrote:
> On Wed, Apr 15, 2020 at 10:18:16AM +0100, Richard Sandiford wrote:
> > luoxhu--- via Gcc-patches writes:
> > > -count = simplify_gen_binary (PLUS, mode, count, const1_rtx);
> > > +{
> > > + /* Fold (add -1;
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=94633
--- Comment #2 from Ian Lance Taylor ---
See https://gcc.gnu.org/PR94611 and https://gcc.gnu.org/PR94466.
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=94626
Martin Sebor changed:
What|Removed |Added
CC||msebor at gcc dot gnu.org
Next try – with the proper patch instead of a full test case.
On 4/17/20 5:54 PM, Tobias Burnus wrote:
It turned out that doing
omp enter data map(alloc:FortranArray)
omp exit data map(delete:FortranArray)
left the array descriptor (fortranarray [as opposed to
fortranarray.data])
on the
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=94631
--- Comment #5 from Rich Felker ---
No, GCC's treatment also seems to mess up bitfields smaller than int and fully
governed by the standard (no implementation-defined use of non-int types):
struct foo {
unsigned x:31;
};
struct foo bar =
It turned out that doing
omp enter data map(alloc:FortranArray)
omp exit data map(delete:FortranArray)
left the array descriptor (fortranarray [as opposed to fortranarray.data])
on the device. (cf. -fdump-tree-omplower in the PR.)
Mapping FortranArray again (e.g. "map(tofrom:FortranArray)")
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=90392
Jeffrey A. Law changed:
What|Removed |Added
Summary|[9/10 Regression] Assertion |[8/9/10 Regression]
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=90983
--- Comment #3 from Torsten Robitzki ---
Is there a workaround to disable that warning (once it was enabled) for the
case, gcc detects an unbound stack usage?
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=94630
--- Comment #6 from Segher Boessenkool ---
Please mention in the TITLE that this is ONLY for the ELFv2 ABI?
Some more C++20 changes from P1614R2, "The Mothership has Landed".
This adds three-way comparison support to std::char_traits,
std::basic_string, std::basic_string_view, and std::sub_match.
* include/bits/basic_string.h (basic_string): Define operator<=> and
remove redundant
This patch fixes a large lmbench performance regression with
128-bit SVE, compiled in length-agnostic mode.
vect_better_loop_vinfo_p (new in GCC 10) tries to estimate whether
a new loop_vinfo is cheaper than a previous one, with an in-built
preference for the old one. For variable VF it prefers
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=94636
Martin Liška changed:
What|Removed |Added
Keywords|easyhack|
Target Milestone|---
On Wed, Apr 8, 2020 at 9:41 AM Jeff Law wrote:
>
> On Wed, 2020-04-08 at 09:23 -0700, H.J. Lu wrote:
> > On Wed, Apr 8, 2020 at 9:16 AM Jeff Law wrote:
> > > On Tue, 2020-03-31 at 08:11 -0700, H.J. Lu via Gcc-patches wrote:
> > > > Since constant_call_address_operand has
> > > >
> > > > ;; Test
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=94578
--- Comment #9 from Thomas Koenig ---
Here's what a solution could look like. I am not really sure that this
is the way to go, there may be some corner cases (pointer to an
argument which was passed as a transposed argument?) which this
might
1 - 100 of 218 matches
Mail list logo
