https://gcc.gnu.org/bugzilla/show_bug.cgi?id=114107
--- Comment #11 from Hongtao Liu ---
(In reply to N Schaeffer from comment #9)
> In addition, optimizing for size with -Os leads to a non-vectorized
> double-loop (51 bytes) while the vectorized loop with vbroadcastsd (produced
> by clang -Os)
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=114107
--- Comment #10 from N Schaeffer ---
intrestingly (and maybe surprisingly) I can get gcc to produce nearly optimal
code using vbroadcastsd with the following options:
-O2 -march=skylake -ftree-vectorize
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=114070
Richard Biener changed:
What|Removed |Added
Priority|P3 |P2
Summary|[12/13/14
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=114070
--- Comment #8 from GCC Commits ---
The master branch has been updated by Richard Biener :
https://gcc.gnu.org/g:af66ad89e8169f44db723813662917cf4cbb78fc
commit r14-9173-gaf66ad89e8169f44db723813662917cf4cbb78fc
Author: Richard Biener
Date:
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=114107
--- Comment #9 from N Schaeffer ---
In addition, optimizing for size with -Os leads to a non-vectorized double-loop
(51 bytes) while the vectorized loop with vbroadcastsd (produced by clang -Os)
leads to 40 bytes.
It is thus also a missed
The following properly guards the simplifications that move
operations into VEC_CONDs, in particular when that changes the
type constraints on this operation.
This needed a genmatch fix which was recording spurious implicit fors
when tcc_comparison is used in a C expression.
Bootstrapped and
> validate_subreg is a can of worms, can you try to fix the issue in DSE
> by avoiding to form the subreg in the first place?
Sure thing, will have a try in v2.
Pan
-Original Message-
From: Richard Biener
Sent: Monday, February 26, 2024 3:38 PM
To: Li, Pan2
Cc:
On Mon, Feb 26, 2024 at 4:26 AM wrote:
>
> From: Pan Li
>
> We allowed vector type for get_stored_val when read is less than or
> equal to store in previous. Unfortunately, we missed to adjust the
> validate_subreg part accordingly. For vector type, we don't need to
> restrict the mode size is
diff --git a/gcc/tree-vect-stmts.cc b/gcc/tree-vect-stmts.cc
index 1dbe1115da4..6303d82d959 100644
--- a/gcc/tree-vect-stmts.cc
+++ b/gcc/tree-vect-stmts.cc
@@ -11521,7 +11521,8 @@ vectorizable_load (vec_info *vinfo,
- (vec_num * j + i) * nunits);
Hi!
These 2 patterns are incorrect on floating point, or for -fwrapv, or
for -ftrapv, or the first one for unsigned types (the second one is
mathematically correct, but we ought to just fold that to 0 instead).
So, the following patch properly guards this.
I think we don't need &&
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=114099
--- Comment #8 from Tamar Christina ---
Created attachment 57537
--> https://gcc.gnu.org/bugzilla/attachment.cgi?id=57537=edit
uses.patch
new code seems sensitive to visitation order as get_virtual_phi returns NULL
for blocks which don't
Hi!
In the following testcase we infinitely recurse during BIT_IOR_EXPR
reassociation.
One operand is (unsigned _BitInt(31)) a << 4 and another operand
2147483647 >> 1 | 80 where both the right shift and the | 80
trees have TREE_CONSTANT set, but weren't folded because of delayed
folding, where
On Fri, Feb 23, 2024 at 3:48 AM Palmer Dabbelt wrote:
>
> On Wed, 21 Feb 2024 16:02:50 PST (-0800), Kito Cheng wrote:
> > Palmer Dabbelt 於 2024年2月22日 週四 07:42 寫道：
> >
> >> On Wed, 21 Feb 2024 15:34:32 PST (-0800), Kito Cheng wrote:
> >> > LGTM for the patch
> >> >
> >> > Li, Pan2 於 2024年2月21日
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=114094
Jakub Jelinek changed:
What|Removed |Added
Resolution|--- |FIXED
Status|ASSIGNED
Hi!
In my r14-8214 changes I apparently forgot one \n at the end of an instruction.
The corresponding AT line looks like:
"1:\tcall\t*%s@GOTPCREL(%%rip)\n"
but the Intel variant was
"1:\tcall\t[QWORD PTR %s@GOTPCREL[rip]]"
Fixed thusly, bootstrapped/regtested on x86_64-linux and i686-linux,
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=114094
--- Comment #2 from GCC Commits ---
The master branch has been updated by Jakub Jelinek :
https://gcc.gnu.org/g:6987f16742bd4fc6bb8118b9efde52fb9169b327
commit r14-9172-g6987f16742bd4fc6bb8118b9efde52fb9169b327
Author: Jakub Jelinek
Date:
Got it, we need to combine that together up to point.
Thanks Tamar for the explanation. Help a lot and will have a try in v3.
Pan
-Original Message-
From: Tamar Christina
Sent: Sunday, February 25, 2024 5:02 PM
To: Li, Pan2 ; gcc-patches@gcc.gnu.org
Cc: juzhe.zh...@rivai.ai; Wang,
Add proper hints for implicit declaration of strerror.
The results could be confusing depending on the other included headers.
These example messages are from compiling a trivial program to print the
string for an errno value. It only includes stdio.h (cstdio for C++).
Before:
$
Hi All,
The following patch has been bootstrapped and regtested on powerpc64le-linux.
There is no immediate value splatting instruction in powerpc. Currently that
needs to be stored in a register or memory. For addressing this I have updated
the predicate for the second operand in vsx_splat to
Hi All,
The following patch has been bootstrapped and regtested on powerpc64le-linux.
PR110040 exposes an issue concerning moves from vector registers to GPRs.
There are two moves, one for upper 64 bits and the other for the lower
64 bits. In the problematic test case, we are only interested in
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=114108
Andrew Pinski changed:
What|Removed |Added
Last reconfirmed||2024-02-26
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=114108
--- Comment #3 from Andrew Pinski ---
Created attachment 57536
--> https://gcc.gnu.org/bugzilla/attachment.cgi?id=57536=edit
Reduced testcase
Just needs -O3 as mentioned.
On Mon, Feb 26, 2024 at 11:42 AM Li, Pan2 wrote:
>
> > Be Careful, It may regresses some other backend.
>
> Thanks Hongtao, how about take INNER_MODE here for regsize. Currently it will
> be the whole vector register when comparation.
>
> poly_uint64 regsize = REGMODE_NATURAL_SIZE (imode);
>
>
Add option -m(no-)autovec-segment to enable/disable autovectorizer
from emitting vector segment load/store instructions. This is useful for
performance experiments.
gcc/ChangeLog:
* config/riscv/autovec.md (vec_mask_len_load_lanes,
vec_mask_len_store_lanes):
Predicate with
The specification of crc/crcc instructions is clear that the output is
sign-extended to GRLEN. Add a define_insn to tell the compiler this
fact and allow it to remove the unneeded sign extension on crc/crcc
output. As crc/crcc instructions are usually used in a tight loop,
this should produce a
Introduce an iterator for UNSPEC_CRC and UNSPEC_CRCC to make the next
change easier.
gcc/ChangeLog:
* config/loongarch/loongarch.md (CRC): New define_int_iterator.
(crc): New define_int_attr.
(loongarch_crc_w__w, loongarch_crcc_w__w): Unify
into ...
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=114098
--- Comment #3 from GCC Commits ---
The master branch has been updated by H.J. Lu :
https://gcc.gnu.org/g:4972f97a265c574d51e20373ddefd66576051e5c
commit r14-9171-g4972f97a265c574d51e20373ddefd66576051e5c
Author: H.J. Lu
Date: Sun Feb 25
On Sun, Feb 25, 2024 at 7:03 PM Hongtao Liu wrote:
>
> On Mon, Feb 26, 2024 at 10:37 AM H.J. Lu wrote:
> >
> > On Sun, Feb 25, 2024 at 6:03 PM Hongtao Liu wrote:
> > >
> > > On Mon, Feb 26, 2024 at 5:11 AM H.J. Lu wrote:
> > > >
> > > > ldtilecfg and sttilecfg take a 512-byte memory block.
> Be Careful, It may regresses some other backend.
Thanks Hongtao, how about take INNER_MODE here for regsize. Currently it will
be the whole vector register when comparation.
poly_uint64 regsize = REGMODE_NATURAL_SIZE (imode);
Pan
-Original Message-
From: Hongtao Liu
Sent: Monday,
On Mon, Feb 26, 2024 at 11:26 AM wrote:
>
> From: Pan Li
>
> We allowed vector type for get_stored_val when read is less than or
> equal to store in previous. Unfortunately, we missed to adjust the
> validate_subreg part accordingly. For vector type, we don't need to
> restrict the mode size
Hi,
This patch tries to fix a potential problem which is raised by the patch
for PR111267. The volatile asm operand tries to be propagated to a single
set insn with the patch for PR111267. It has potential risk as the behavior
is wrong. Currently set_src_cost comparison can reject such
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=114107
--- Comment #8 from Hongtao Liu ---
(In reply to Hongtao Liu from comment #7)
> perm_cost is very low in x86 backend, and it maybe ok for 128-bit vectors,
> pshufb/shufps are avaible for most cases.
> But for 256/512-bit vectors, when the
From: Pan Li
We allowed vector type for get_stored_val when read is less than or
equal to store in previous. Unfortunately, we missed to adjust the
validate_subreg part accordingly. For vector type, we don't need to
restrict the mode size is greater than the vector register size.
Thus, for
On Mon, Feb 26, 2024 at 10:37 AM H.J. Lu wrote:
>
> On Sun, Feb 25, 2024 at 6:03 PM Hongtao Liu wrote:
> >
> > On Mon, Feb 26, 2024 at 5:11 AM H.J. Lu wrote:
> > >
> > > ldtilecfg and sttilecfg take a 512-byte memory block. With
> > > _tile_loadconfig implemented as
> > >
> > > extern __inline
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=114107
Hongtao Liu changed:
What|Removed |Added
CC||liuhongt at gcc dot gnu.org
--- Comment
On Sun, Feb 25, 2024 at 6:03 PM Hongtao Liu wrote:
>
> On Mon, Feb 26, 2024 at 5:11 AM H.J. Lu wrote:
> >
> > ldtilecfg and sttilecfg take a 512-byte memory block. With
> > _tile_loadconfig implemented as
> >
> > extern __inline void
> > __attribute__((__gnu_inline__, __always_inline__,
Hi,
This patch enables overlap memory store for block memory clear which
saves the number of store instructions. The expander calls
widest_fixed_size_mode_for_block_clear to get the mode for looped block
clear and calls widest_fixed_size_mode_for_block_clear to get the mode
for last overlapped
> Date: Fri, 16 Feb 2024 11:16:22 +0100
> From: Jakub Jelinek
> Given the recent discussions on IRC started with Andrew P. mentioning that
> an asm goto outputs test should have { target lra } and the lra effective
> target in GCC 11/12 only returning 0 for PA and in 13/14 for PA/AVR, while
> we
On Mon, Feb 26, 2024 at 5:11 AM H.J. Lu wrote:
>
> ldtilecfg and sttilecfg take a 512-byte memory block. With
> _tile_loadconfig implemented as
>
> extern __inline void
> __attribute__((__gnu_inline__, __always_inline__, __artificial__))
> _tile_loadconfig (const void *__config)
> {
> __asm__
On Wed, Feb 7, 2024 at 4:23 AM Matteo Italia wrote:
>
> Il 06/02/24 10:17, Jonathan Yong ha scritto:
> > On 2/6/24 05:31, NightStrike wrote:
> >> On Mon, Feb 5, 2024, 06:53 Matteo Italia wrote:
> >>
> >>> Il 31/01/24 04:24, LIU Hao ha scritto:
> 在 2024-01-31 08:08, Jonathan Yong 写道:
> >
On Wed, Feb 21, 2024 at 12:48 PM Evgeny Karpov
wrote:
>
> Hello,
>
> We would like to take your attention to the review of changes for the
> new GCC target, aarch64-w64-mingw32. The new target will be
> supported, tested, added to CI, and maintained by Linaro. This marks
> the first of three
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=114105
--- Comment #7 from Mark Millard ---
(In reply to Andrew Pinski from comment #6)
> . . .
> It is documented here:
> https://gcc.gnu.org/install/prerequisites.html
>
> "To build all languages in a cross-compiler or other configuration where
>
Thanks for fixing this! Didn't notice that the pointer conversion can
cause this issue...
Was it possible to use local array like
char a[64] = (char *)p
__asm__ volatile ("ldtilecfg\t%X0" :: "m" (a)));
If not, for the two patterns we can use "m" instead of "jm" as APX
supports EGPR extension
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=114105
--- Comment #6 from Andrew Pinski ---
(In reply to Mark Millard from comment #5)
> (In reply to Andrew Pinski from comment #2)
> > . . .
> > >Part of the reason FreeBSD puts effort into making --disable-bootstrap work
> > This should not be
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=114108
--- Comment #2 from Andrew Pinski ---
Just -O3 is enough.
Reducing
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=114105
--- Comment #5 from Mark Millard ---
(In reply to Andrew Pinski from comment #2)
> . . .
> >Part of the reason FreeBSD puts effort into making --disable-bootstrap work
> This should not be done unless you are building with GCC itself. The
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=114108
Andrew Pinski changed:
What|Removed |Added
CC||pinskia at gcc dot gnu.org
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=114108
--- Comment #1 from Sam James ---
I can reproduce it with `g++ -c arithm.dispatch.cpp.ii -O3
-mcpu=neoverse-n1+crc+crypto+ssbs`. I can't try to narrow it down or reduce it
right now though.
le-vtable-verify --disable-libvtv --with-zstd --without-isl
--enable-default-pie --enable-host-pie --enable-host-bind-now
--enable-default-ssp --disable-fixincludes
Thread model: posix
Supported LTO compression algorithms: zlib zstd
gcc version 14.0.1 20240225 (exp
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=114073
Andrew Pinski changed:
What|Removed |Added
CC||zsojka at seznam dot cz
--- Comment #4
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=114096
Andrew Pinski changed:
What|Removed |Added
Status|UNCONFIRMED |RESOLVED
Resolution|---
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=114107
--- Comment #6 from N Schaeffer ---
indeed, aarch64 assembly looks very good.
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=114107
--- Comment #5 from Andrew Pinski ---
(In reply to N Schaeffer from comment #3)
> If this is a cost model problem, it is a bad one.
It is almost definitely a cost model in the x86_64 backend issue. Because I
tried on aarch64 with
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=114107
--- Comment #4 from N Schaeffer ---
... and thank you for your quick reply!
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=114107
--- Comment #3 from N Schaeffer ---
I have not benchmarked.
For 4 vmulpd doing the actual work, there are more than 40 permute/mov
instructions, among which 24 vpermd instructions which have a 3 cycle latency.
That is 6 vpermd per vmulpd.
There
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=114107
Andrew Pinski changed:
What|Removed |Added
Target||x86_64-linux
--- Comment #2 from
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=114107
--- Comment #1 from Andrew Pinski ---
Created attachment 57534
--> https://gcc.gnu.org/bugzilla/attachment.cgi?id=57534=edit
Full testcase
`-O3 -march=skylake`
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=114099
Andrew Pinski changed:
What|Removed |Added
CC||tnfchris at gcc dot gnu.org
---
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=114107
Bug ID: 114107
Summary: poor vectorization at -O3 when dealing with arrays of
different multiplicity, good with -O2
Product: gcc
Version: 13.2.0
Status: UNCONFIRMED
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=114099
Andrew Pinski changed:
What|Removed |Added
Last reconfirmed||2024-02-25
Keywords|
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=114099
Andrew Pinski changed:
What|Removed |Added
Attachment #57527|0 |1
is obsolete|
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=114104
--- Comment #3 from Jonathan Wakely ---
I don't care whether GCC synthesizes an operator!= that inherits the nodiscard
attribute, or it generates a discarded bool using the built-in !, but there
needs to be a warning either way.
Currently a
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=114099
--- Comment #4 from Andrew Pinski ---
Created attachment 57532
--> https://gcc.gnu.org/bugzilla/attachment.cgi?id=57532=edit
Reduced further but still has undefined code in it
On 2/25/24 12:26 PM, Harald Anlauf wrote:
Dear all,
the attached simple patch fixes an issue where we evaluated
polymorphic functions twice in assignments: once for the _data
component, and once for the _vptr. Using save_expr prevents
the double evaluation.
Regtested on x86_64-pc-linux-gnu.
Hi,
This patch merges the D front-end and runtime library with upstream dmd
ceff48bf7d, and the standard library with phobos dcbfbd43a.
D front-end changes:
- Import latest fixes from dmd v2.107.1-rc.1.
D runtime changes:
- Import latest fixes from druntime v2.107.1-rc.1.
On 2/25/24 12:34 PM, Harald Anlauf wrote:
Hi Jerry,
On 2/22/24 20:11, Jerry D wrote:
Hi all,
The attached fix adds a check for an error condition from a UDDTIO
procedure in the case where there is no actual underlying error, but the
user defines an error by setting the iostat variable
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=105456
--- Comment #5 from GCC Commits ---
The master branch has been updated by Jerry DeLisle :
https://gcc.gnu.org/g:3f58f96a4e8255e222953f9856bcd6c25f7b33cd
commit r14-9168-g3f58f96a4e8255e222953f9856bcd6c25f7b33cd
Author: Jerry DeLisle
Date:
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=114099
--- Comment #3 from Andrew Pinski ---
Note the reduced testcase is undefined code.
c::j is not initialized when c::k() is called.
Snapshot gcc-14-20240225 is now available on
https://gcc.gnu.org/pub/gcc/snapshots/14-20240225/
and on various mirrors, see https://gcc.gnu.org/mirrors.html for details.
This snapshot has been generated from the GCC 14 git branch
with the following options: git://gcc.gnu.org/git/gcc.git branch
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=114106
Andrew Pinski changed:
What|Removed |Added
Keywords||c++-lambda
Blocks|
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=114106
Bug ID: 114106
Summary: Wrong result of decltype
Product: gcc
Version: 14.0
Status: UNCONFIRMED
Severity: normal
Priority: P3
Component: c++
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=114101
--- Comment #7 from dave.anglin at bell dot net ---
On 2024-02-25 4:04 p.m., dave.anglin at bell dot net wrote:
> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=114101
>
> --- Comment #6 from dave.anglin at bell dot net ---
> The for HP-UX
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=104342
--- Comment #6 from Eric Botcazou ---
> That thought occurred to me, but does that mean that if this code is
> compiled with a release branch Bad Things will happen? (I guess the code
> would probably have to get executed for that to occur)
On 23/2/24 17:54, Andrew Pinski wrote:
There is arm64ec ABI defined for aarch64 windows which is a different
ABI from the standard windows aarch64 ABI, though I am not sure if it
supported with the patches here.
It is documented at
ix86_set_func_type checks noreturn attribute to avoid incompatible
attribute error in LTO1 on interrupt functions. Since TREE_THIS_VOLATILE
is set also for _Noreturn without noreturn attribute, check interrupt
attribute for interrupt functions instead.
gcc/
PR target/114097
*
On 22/2/24 11:11, Richard Earnshaw (lists) wrote:
Most of the free world has left COFF behind since several decades, so I won't
comment on that. YMMV.
This isn't helpful. Windows platforms use (a derivative of) COFF, so that's
what the tools need to use when targetting that platform.
Also,
ldtilecfg and sttilecfg take a 512-byte memory block. With
_tile_loadconfig implemented as
extern __inline void
__attribute__((__gnu_inline__, __always_inline__, __artificial__))
_tile_loadconfig (const void *__config)
{
__asm__ volatile ("ldtilecfg\t%X0" :: "m" (*((const void **)__config)));
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=114101
--- Comment #6 from dave.anglin at bell dot net ---
The for HP-UX doesn't do this sort of thing:
> extern double acos(double __x) __ATTR_CONST__;
> #define acosf acos /**< The alias for acos(). */
>
> Technically, avr doesn't have
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=104342
--- Comment #5 from simon at pushface dot org ---
That thought occurred to me, but does that mean that if this code is compiled
with a release branch Bad Things will happen? (I guess the code would probably
have to get executed for that to
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=114105
--- Comment #4 from Sam James ---
(In reply to Sam James from comment #3)
> I have a patch which includes those extra hunks (in addition to the PR111632
> one), but didn't have a chance yet to look at iain's build failure on darwin.
(someone
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=114105
--- Comment #3 from Sam James ---
I have a patch which includes those extra hunks (in addition to the PR111632
one), but didn't have a chance yet to look at iain's build failure on darwin.
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=114104
Harald van Dijk changed:
What|Removed |Added
CC||harald at gigawatt dot nl
---
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=114105
--- Comment #2 from Andrew Pinski ---
Something like:
```
diff --git a/gcc/jit/dummy-frontend.cc b/gcc/jit/dummy-frontend.cc
index dbeeacd17a8..f57fb805a5f 100644
--- a/gcc/jit/dummy-frontend.cc
+++ b/gcc/jit/dummy-frontend.cc
@@ -18,6 +18,7 @@
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=114105
--- Comment #1 from Andrew Pinski ---
`#define INCLUDE_VECTOR` should be done for jit ...
And maybe libcc1 too.
Dear all,
just like last year, I would like to commit the changes that took place
over at GNAT for GCC v14. The patch is attached to the email. Hopefully
it is good enough to just be added to master. If you see something wrong
or if you would like to add anything to it, feel free :) Feedback
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=114105
Bug ID: 114105
Summary: --disable-bootstrap based builds vs libcc1 and gcc/jit
use of gcc/system.h poisoning policy
Product: gcc
Version: 14.0
Status: UNCONFIRMED
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=114101
--- Comment #5 from John David Anglin ---
Test results without patch:
https://gcc.gnu.org/pipermail/gcc-testresults/2024-February/808830.html
=== libstdc++ tests ===
Running target unix
FAIL: 19_diagnostics/stacktrace/current.cc
Harald,
Thank you for reviewing my code. I've been doing research and debugging to
investigate the error thrown by Intel and NAG for the deferred parameter in
the dummy variable declaration. I found where the problem was and added the
fix as part of my patch. I've attached the patch as a file,
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=114012
anlauf at gcc dot gnu.org changed:
What|Removed |Added
Status|NEW |ASSIGNED
--- Comment #3
Hi Jerry,
On 2/22/24 20:11, Jerry D wrote:
Hi all,
The attached fix adds a check for an error condition from a UDDTIO
procedure in the case where there is no actual underlying error, but the
user defines an error by setting the iostat variable manually before
returning to the parent READ.
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=114101
--- Comment #4 from dave.anglin at bell dot net ---
On 2024-02-25 2:21 p.m., redi at gcc dot gnu.org wrote:
> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=114101
>
> Jonathan Wakely changed:
>
> What|Removed
Dear all,
the attached simple patch fixes an issue where we evaluated
polymorphic functions twice in assignments: once for the _data
component, and once for the _vptr. Using save_expr prevents
the double evaluation.
Regtested on x86_64-pc-linux-gnu. OK for mainline?
And a backport to 13-branch
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=114101
--- Comment #3 from dave.anglin at bell dot net ---
On 2024-02-25 2:21 p.m., redi at gcc dot gnu.org wrote:
> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=114101
>
> Jonathan Wakely changed:
>
> What|Removed
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=114101
--- Comment #2 from dave.anglin at bell dot net ---
On 2024-02-25 2:17 p.m., redi at gcc dot gnu.org wrote:
> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=114101
>
> Jonathan Wakely changed:
>
> What|Removed
Hi Mike, Joseph,
On Sun, Feb 25, 2024 at 10:10:09AM -0800, Mike Stump wrote:
> On Feb 6, 2024, at 2:45 AM, Alejandro Colomar wrote:
> >
> > Warn about the following:
> >
> >char s[3] = "foo";
>
> No ObjC specific impact here, so no need for ObjC review.
>
> As a member of the peanut
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=114012
anlauf at gcc dot gnu.org changed:
What|Removed |Added
CC||anlauf at gcc dot gnu.org
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=114104
Jonathan Wakely changed:
What|Removed |Added
Status|UNCONFIRMED |NEW
Ever confirmed|0
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=114104
Bug ID: 114104
Summary: nodiscard not diagnosed on synthesized operator!=
Product: gcc
Version: 14.0
Status: UNCONFIRMED
Keywords: diagnostic
Severity: normal
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=114100
Andrew Pinski changed:
What|Removed |Added
Severity|normal |enhancement
Ever confirmed|0
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=104342
Eric Botcazou changed:
What|Removed |Added
Summary|[14 regression] ICE with|ICE with -gnata
1 - 100 of 152 matches
Mail list logo
