https://gcc.gnu.org/bugzilla/show_bug.cgi?id=105606
--- Comment #4 from Joel Johnson ---
> Wait you didn't mention you needed -std=c++20 to get the failure.
Ah indeed, my apologies!
I'm unable to reproduce the Clang failure using -std=c++20, at least in a quick
godbolt check at https://godbolt.
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=105606
Andrew Pinski changed:
What|Removed |Added
Resolution|--- |DUPLICATE
Status|UNCONFIRME
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=102199
Andrew Pinski changed:
What|Removed |Added
CC||mrjoel at lixil dot net
--- Comment #8
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=105606
--- Comment #6 from Andrew Pinski ---
(In reply to Joel Johnson from comment #4)
> > Wait you didn't mention you needed -std=c++20 to get the failure.
>
> Ah indeed, my apologies!
>
> I'm unable to reproduce the Clang failure using -std=c++20,
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=105607
Bug ID: 105607
Summary: sh-unknown-elf: Error: opcode not valid for this cpu
variant
Product: gcc
Version: 12.1.0
Status: UNCONFIRMED
Severity: normal
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=105601
--- Comment #13 from tt_1 ---
Created attachment 52979
--> https://gcc.gnu.org/bugzilla/attachment.cgi?id=52979&action=edit
verbose output with -v and binutils-2.38
don't see any difference with binutils-2.38?
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=105607
--- Comment #1 from Andrew Pinski ---
>The same configuration/build recipe successfully builds GCC 11.3.0
Did you change binutils too or they kept the same?
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=105607
--- Comment #2 from Chris Packham ---
binutils is the same but I did update the kernel headers.
_LTO_WRAPPER=/tmp/gb/gcc/lto-wrapper
Target: x86_64-pc-linux-gnu
Configured with: <>/configure --disable-multilib --disable-bootstrap
--with-native-system-header-dir=/<>/glibc-2.34-115-dev/include
--prefix=/tmp/gb/__td__ CFLAGS='-O1 -ggdb3' CXXFLAGS='-O1 -ggdb3' LDFLAGS='-O1
-ggdb3'
Thread model: posix
Supported LTO compression algorithms: zlib
gcc version 13.0.0 20220515 (experimental) (GCC)
/lto-wrapper
Target: x86_64-pc-linux-gnu
Configured with: <>/configure --disable-multilib --disable-bootstrap
--with-native-system-header-dir=/<>/glibc-2.34-115-dev/include
--prefix=/tmp/gb/__td__ CFLAGS='-O1 -ggdb3' CXXFLAGS='-O1 -ggdb3' LDFLAGS='-O1
-ggdb
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=105607
--- Comment #3 from Chris Packham ---
Just blindly comparing log files between a good and a bad build the `-mb -m1`
combination appears to be new and is the one causing problems.
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=105607
--- Comment #4 from Andrew Pinski ---
Can you provide the exact configure options you used?
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=105607
--- Comment #5 from Andrew Pinski ---
The only change I have saw to the sh specific files which would affect was in
t-linux but that would be linux only, this is elf.
r12-6929-g06995c2958aaae
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=105607
--- Comment #6 from Chris Packham ---
Here's the relevant snippet from the log.
CC_FOR_BUILD='x86_64-build_pc-linux-gnu-gcc' CFLAGS='-O2 -g
-I/home/runner/work/crosstool-ng/crosstool-ng/.build/sh-unknown-elf/buildtools/include
' CFLAGS_FOR_BUI
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=105473
--- Comment #8 from harper at msor dot vuw.ac.nz ---
Thank you. Unfortunately I think you found some but not all of what the
standard says about semicolons as separators. You will recall that my
original bug report had a program compiled with std
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=105607
--- Comment #7 from Chris Packham ---
There's also
https://gcc.gnu.org/git/?p=gcc.git;a=commit;h=081c9dfb67a0d2e7425ddb5420ada588026f92ca
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=105607
--- Comment #8 from Andrew Pinski ---
(In reply to Chris Packham from comment #7)
> There's also
> https://gcc.gnu.org/git/?p=gcc.git;a=commit;
> h=081c9dfb67a0d2e7425ddb5420ada588026f92ca
That should not have an effect on the multi-libs compil
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=105609
Bug ID: 105609
Summary: ranges::move(_backward) should use ranges::iter_move
instead of std::move
Product: gcc
Version: 12.0
Status: UNCONFIRMED
Severity:
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=105607
--- Comment #9 from Chris Packham ---
(In reply to Andrew Pinski from comment #8)
> (In reply to Chris Packham from comment #7)
> > There's also
> > https://gcc.gnu.org/git/?p=gcc.git;a=commit;
> > h=081c9dfb67a0d2e7425ddb5420ada588026f92ca
>
>
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=105610
Bug ID: 105610
Summary: warn about cv qualifiers ignored for a base class
Product: gcc
Version: 12.0
Status: UNCONFIRMED
Severity: normal
Priority: P3
Component
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=105473
--- Comment #9 from Jerry DeLisle ---
Thank you for digging out the standards references. That was going to be my
next step as the standards are notorious for these kinds of tidbits and corner
cases. I have been reviewing the code implementatio
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=105601
--- Comment #14 from tt_1 ---
any objections to reporting this to binutils bugzilla at sourceware?
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=105473
--- Comment #10 from Jerry DeLisle ---
Just completed good regression testing and have this:
testinput = "1;17;3.14159"
At line 8 of file pr105473.f90
Fortran runtime error: Semicolon not allowed as separator with DECIMAL='point'
Now I
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=105589
Jason Merrill changed:
What|Removed |Added
Priority|P3 |P1
Keywords|
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=105589
Jason Merrill changed:
What|Removed |Added
Keywords|patch |
--- Comment #3 from Jason Merrill ---
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=105492
Jason Merrill changed:
What|Removed |Added
Keywords||ice-on-valid-code, patch
Prio
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=105589
--- Comment #4 from CVS Commits ---
The master branch has been updated by Jason Merrill :
https://gcc.gnu.org/g:ce46d6041358052dfa26f3720732f0357c5d72e7
commit r13-463-gce46d6041358052dfa26f3720732f0357c5d72e7
Author: Jason Merrill
Date: Fr
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=105191
--- Comment #4 from CVS Commits ---
The master branch has been updated by Jason Merrill :
https://gcc.gnu.org/g:ce46d6041358052dfa26f3720732f0357c5d72e7
commit r13-463-gce46d6041358052dfa26f3720732f0357c5d72e7
Author: Jason Merrill
Date: Fr
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=92385
--- Comment #16 from CVS Commits ---
The master branch has been updated by Jason Merrill :
https://gcc.gnu.org/g:ce46d6041358052dfa26f3720732f0357c5d72e7
commit r13-463-gce46d6041358052dfa26f3720732f0357c5d72e7
Author: Jason Merrill
Date: Fr
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=102651
--- Comment #4 from CVS Commits ---
The releases/gcc-12 branch has been updated by Jason Merrill
:
https://gcc.gnu.org/g:5237059e04d105fe5441fa7434699eea9a34bf1b
commit r12-8378-g5237059e04d105fe5441fa7434699eea9a34bf1b
Author: Jason Merrill
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=49387
--- Comment #10 from CVS Commits ---
The releases/gcc-12 branch has been updated by Jason Merrill
:
https://gcc.gnu.org/g:5237059e04d105fe5441fa7434699eea9a34bf1b
commit r12-8378-g5237059e04d105fe5441fa7434699eea9a34bf1b
Author: Jason Merrill
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=104470
--- Comment #8 from CVS Commits ---
The releases/gcc-12 branch has been updated by Jason Merrill
:
https://gcc.gnu.org/g:73b47159d7811cf1d7aaaf78dbdd141161b93ca3
commit r12-8379-g73b47159d7811cf1d7aaaf78dbdd141161b93ca3
Author: Jason Merrill
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=105589
--- Comment #5 from CVS Commits ---
The releases/gcc-12 branch has been updated by Jason Merrill
:
https://gcc.gnu.org/g:40f749b364b740f41ea6b211f81c21919a2e8bee
commit r12-8380-g40f749b364b740f41ea6b211f81c21919a2e8bee
Author: Jason Merrill
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=105191
--- Comment #5 from CVS Commits ---
The releases/gcc-12 branch has been updated by Jason Merrill
:
https://gcc.gnu.org/g:40f749b364b740f41ea6b211f81c21919a2e8bee
commit r12-8380-g40f749b364b740f41ea6b211f81c21919a2e8bee
Author: Jason Merrill
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=92385
--- Comment #17 from CVS Commits ---
The releases/gcc-12 branch has been updated by Jason Merrill
:
https://gcc.gnu.org/g:40f749b364b740f41ea6b211f81c21919a2e8bee
commit r12-8380-g40f749b364b740f41ea6b211f81c21919a2e8bee
Author: Jason Merrill
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=105589
Jason Merrill changed:
What|Removed |Added
Resolution|--- |FIXED
Status|ASSIGNED
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=100502
--- Comment #6 from CVS Commits ---
The master branch has been updated by Jason Merrill :
https://gcc.gnu.org/g:4df735e01e319997841574f353d2aa076a0335c2
commit r13-465-g4df735e01e319997841574f353d2aa076a0335c2
Author: Jason Merrill
Date: Fr
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=58993
--- Comment #11 from CVS Commits ---
The master branch has been updated by Jason Merrill :
https://gcc.gnu.org/g:4df735e01e319997841574f353d2aa076a0335c2
commit r13-465-g4df735e01e319997841574f353d2aa076a0335c2
Author: Jason Merrill
Date: Fr
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=100932
--- Comment #2 from Nicolas Boulenguez ---
I fail to understand how your answer helps anyone.
Currently, 'autoconf' fails and 'autoconf -I../config' succeeds.
With the change, both would succeed and be equivalent.
What is the benefit of requiri
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=105557
Eric Gallager changed:
What|Removed |Added
CC||egallager at gcc dot gnu.org
--- Commen
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=105611
Bug ID: 105611
Summary: std::shift_left/right should not use ranges::next
Product: gcc
Version: 12.0
Status: UNCONFIRMED
Severity: normal
Priority: P3
Component
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=93082
--- Comment #8 from Bruce Korb ---
It should not be terribly difficult to add another include tree for fixinc to
search. Also, unless 32 is cast as forever being the only value
kAuthorizationExternalFormLength could possibly ever have:
selec
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=93082
--- Comment #9 from Bruce Korb ---
Um, I didn't finish my misthink for item#1 above. Please ignore. :)
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=93082
--- Comment #10 from Iain Sandoe ---
I also have a few "clang compatibility workarounds" for GCC (including one for
this specific case) - but they need putting behind some "-fclang-compatibility"
flag or so.
Hopefully, will work on integrating t
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=93082
--- Comment #11 from Iain Sandoe ---
Created attachment 52980
--> https://gcc.gnu.org/bugzilla/attachment.cgi?id=52980&action=edit
work in progress patch for this case
* this is not finished (needs to be conditional on a compatibility flag)
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=83907
Roger Sayle changed:
What|Removed |Added
Status|ASSIGNED|RESOLVED
Known to work|
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=83819
Bug 83819 depends on bug 83907, which changed state.
Bug 83907 Summary: missing strlen optimization for non-zero memset followed by
a nul byte store
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=83907
What|Removed
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=105243
kargl at gcc dot gnu.org changed:
What|Removed |Added
Status|UNCONFIRMED |NEW
Last reconfirmed|
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=105473
--- Comment #11 from harper at msor dot vuw.ac.nz ---
Thank you Jerry. Commas as separators with DECIMAL = 'comma' may be
trickier because commas then do the job that decimal points normally do,
and they cannot act as separators.
Here is a litt
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=105587
--- Comment #3 from CVS Commits ---
The master branch has been updated by hongtao Liu :
https://gcc.gnu.org/g:69c4b5c519f0df37e4903992644cc29682721bc1
commit r13-468-g69c4b5c519f0df37e4903992644cc29682721bc1
Author: liuhongt
Date: Fri May 1
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=105473
--- Comment #12 from Jerry DeLisle ---
Created attachment 52981
--> https://gcc.gnu.org/bugzilla/attachment.cgi?id=52981&action=edit
Prposed Patch to add checks for 'comma' and 'point'
This patch is pretty close. It does regression test OK.
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=105587
--- Comment #4 from Hongtao.liu ---
Fixed in GCC13.
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=105473
--- Comment #13 from Jerry DeLisle ---
With John's multiple combinations test case I get the following results with
the attached patch. All places where we gave an error before the patch, we give
errors now plus new errors
$ gfc multi.f90
$ ./
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=105473
--- Comment #14 from Jerry DeLisle ---
The first set of results in in Comment #13 is with the line that prints msg
commented out. The second set is with the msg prints.
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=105612
Bug ID: 105612
Summary: [meta-bug] bogus/missing -Wtautological-compare
Product: gcc
Version: 12.0
Status: UNCONFIRMED
Keywords: diagnostic, meta-bug
Severity: normal
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=87504
Eric Gallager changed:
What|Removed |Added
Status|ASSIGNED|WAITING
--- Comment #10 from Eric Gallag
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=105473
--- Comment #15 from harper at msor dot vuw.ac.nz ---
Thank you. My test program failed to distinguish some bad cases from good
cases; a revised version of the program is below. The important change
was making both elements of x be 666 just bef
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=103743
--- Comment #6 from Jiu Fu Guo ---
Drafted a patch:
https://gcc.gnu.org/pipermail/gcc-patches/2022-May/594702.html
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=105586
Kewen Lin changed:
What|Removed |Added
CC||jskumari at gcc dot gnu.org,
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=105513
--- Comment #5 from Hongtao.liu ---
And for constraint like 'vm', it's different from 'v,m' in calculating mem_cost
which will impact RA when op is REG_P. For 'v,m' mem_cost is just 1 *
frequency, but for 'vm' mem_cost is much bigger(memory_move
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=105473
--- Comment #16 from harper at msor dot vuw.ac.nz ---
I have now used ifort on my latest test program, which you should
already have, in the hope that it helps you. It printed this:
john@johns-laptop:~/Jfh$ ifort testiostat4.f90
Compiling "ifor
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=105613
Bug ID: 105613
Summary: [13 Regression] wrong code with unsigned V1TI
comparison
Product: gcc
Version: 13.0
Status: UNCONFIRMED
Keywords: wrong-code
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=105613
Andrew Pinski changed:
What|Removed |Added
Target Milestone|--- |13.0
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=105613
Andrew Pinski changed:
What|Removed |Added
Ever confirmed|0 |1
Status|UNCONFIRMED
64 matches
Mail list logo
