[Bug d/104738] gdc.test/runnable_cxx/stdint.d FAILs on Solaris
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=104738 Iain Buclaw changed: What|Removed |Added Resolution|--- |FIXED Status|UNCONFIRMED |RESOLVED --- Comment #4 from Iain Buclaw --- Fix committed in r12-7636.
[Bug d/104835] [12 Regression] libphobos fails to build on mips64el-linux-gnu
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=104835 Iain Buclaw changed: What|Removed |Added Status|UNCONFIRMED |RESOLVED Resolution|--- |FIXED --- Comment #5 from Iain Buclaw --- Fix committed in r12-7636.
[Bug d/104742] [12 regression] gdc.test/runnable/sdtor.d FAILs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=104742 Iain Buclaw changed: What|Removed |Added Status|UNCONFIRMED |RESOLVED Resolution|--- |FIXED --- Comment #2 from Iain Buclaw --- Fix committed in r12-7636.
[Bug d/104745] [12 regression] gdc.test/runnable/testaa.d FAILs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=104745 Iain Buclaw changed: What|Removed |Added Status|UNCONFIRMED |RESOLVED Resolution|--- |FIXED --- Comment #3 from Iain Buclaw --- Fix committed in r12-7636.
[Bug target/104901] New: gcc/config/rs6000/mm_malloc.h:46: incorrectLogicOperator
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=104901 Bug ID: 104901 Summary: gcc/config/rs6000/mm_malloc.h:46: incorrectLogicOperator Product: gcc Version: 12.0 Status: UNCONFIRMED Severity: normal Priority: P3 Component: target Assignee: unassigned at gcc dot gnu.org Reporter: dcb314 at hotmail dot com Target Milestone: --- Static analyser cppcheck says: gcc/config/rs6000/mm_malloc.h:46:37: warning: Logical conjunction always evaluates to false: __alignment == __malloc_align && __alignment == __vec_align. [incorrectLogicOperator] Suggest replace && with ||
[Bug target/104901] gcc/config/rs6000/mm_malloc.h:46: incorrectLogicOperator
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=104901 David Binderman changed: What|Removed |Added CC||pc at us dot ibm.com --- Comment #1 from David Binderman --- git blame says: efbb17db52af (Paul A. Clarke 2022-02-16 20:01:41 -0600 46) if (__alignment == __malloc_align && __alignment == __vec_align)
[Bug target/104901] gcc/config/rs6000/mm_malloc.h:46: incorrectLogicOperator
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=104901 --- Comment #2 from Andreas Schwab --- Already present in the first commit 281de9c2d56.
[Bug target/104816] -fcf-protection=branch should generate endbr instead of notrack jumps
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=104816 H.J. Lu changed: What|Removed |Added Attachment #52615|0 |1 is obsolete|| --- Comment #10 from H.J. Lu --- Created attachment 52618 --> https://gcc.gnu.org/bugzilla/attachment.cgi?id=52618&action=edit The v2 patch
[Bug testsuite/103324] RFE: Add a `make quickcheck` or `make smoketest` Makefile target to allow only running a portion of the testsuite
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=103324 --- Comment #5 from Eric Gallager --- (In reply to Eric Gallager from comment #3) > https://gcc.gnu.org/install/test.html says "To get a list of the possible > *.exp files, pipe the output of ‘make check’ into a file and look at the > ‘Running … .exp’ lines." ...has anyone stored their output from doing so > recently? I don't really want to run the entire testsuite just to generate > this list... So, now I'm running the testsuite anyways for other reasons, and one more thing to note is that using any sort of parallelism when running the testsuite (which is pretty much a must these days) makes picking out the ‘Running … .exp’ lines more difficult than necessary...
[Bug target/104890] [12 Regression] fails to build the 32bit libgcc on x86_64-linux-gnu (--enable-cet)
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=104890
H.J. Lu changed:
What|Removed |Added
CC||jakub at redhat dot com
Blocks||104781
--- Comment #5 from H.J. Lu ---
[hjl@gnu-tgl-2 gcc]$ cat x.c
#include
__attribute__((target ("general-regs-only")))
int
foo ()
{
return _get_ssp ();
}
[hjl@gnu-tgl-2 gcc]$ ./xgcc -B./ -S -O2 x.c -mshstk -march=i686 -m32
In file included from ./include/x86gprintrin.h:45,
from x.c:1:
./include/cetintrin.h: In function ‘foo’:
./include/cetintrin.h:47:1: error: inlining failed in call to ‘always_inline’
‘_get_ssp’: target specific option mismatch
47 | _get_ssp (void)
| ^~~~
x.c:7:10: note: called from here
7 | return _get_ssp ();
| ^~~
[hjl@gnu-tgl-2 gcc]$
Referenced Bugs:
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=104781
[Bug 104781] [12 regression] SEGV in _Unwind_GetGR during i386 Ada bootstrap
[Bug target/104890] [12 Regression] fails to build the 32bit libgcc on x86_64-linux-gnu (--enable-cet --with-arch-32=i686)
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=104890 --- Comment #6 from H.J. Lu --- Created attachment 52619 --> https://gcc.gnu.org/bugzilla/attachment.cgi?id=52619&action=edit A patch Please try this.
[Bug target/104890] [12 Regression] fails to build the 32bit libgcc on x86_64-linux-gnu (--enable-cet --with-arch-32=i686)
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=104890 H.J. Lu changed: What|Removed |Added Status|NEW |WAITING Target Milestone|--- |12.0
[Bug target/104890] [12 Regression] fails to build the 32bit libgcc on x86_64-linux-gnu (--enable-cet --with-arch-32=i686)
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=104890
Jakub Jelinek changed:
What|Removed |Added
CC||jakub at gcc dot gnu.org
--- Comment #7 from Jakub Jelinek ---
Comment on attachment 52619
--> https://gcc.gnu.org/bugzilla/attachment.cgi?id=52619
A patch
This looks wrong, it will fail with the same configuration if people build with
-msse2.
The question is why __attribute__((target ("general-regs-only"))) disables
SHSTK.
If that is intentional, we should change to what my first patch proposed, i.e.
"no-sse" instead of "general-regs-only" (or "no-mmx,no-sse").
If it is unintentional, we should fix that.
[Bug target/104890] [12 Regression] fails to build the 32bit libgcc on x86_64-linux-gnu (--enable-cet --with-arch-32=i686)
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=104890 --- Comment #8 from H.J. Lu --- (In reply to Jakub Jelinek from comment #7) > Comment on attachment 52619 [details] > A patch > > This looks wrong, it will fail with the same configuration if people build > with -msse2. I have no issues to build 32-bit GCC with SSE2. I got [hjl@gnu-tgl-2 gcc]$ ./xgcc -B./ -S -O2 -mshstk -march=i686 -m32 /tmp/x.c In file included from ./include/x86gprintrin.h:45, from /tmp/x.c:1: ./include/cetintrin.h: In function ‘foo’: ./include/cetintrin.h:47:1: error: inlining failed in call to ‘always_inline’ ‘_get_ssp’: target specific option mismatch 47 | _get_ssp (void) | ^~~~ /tmp/x.c:7:10: note: called from here 7 | return _get_ssp (); | ^~~ [hjl@gnu-tgl-2 gcc]$ ./xgcc -B./ -S -O2 -mshstk -march=i686 -m32 /tmp/x.c -msse2 [hjl@gnu-tgl-2 gcc]$
[Bug target/104902] New: missing %q in diagnostic
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=104902 Bug ID: 104902 Summary: missing %q in diagnostic Product: gcc Version: 12.0 Status: UNCONFIRMED Keywords: diagnostic Severity: normal Priority: P3 Component: target Assignee: unassigned at gcc dot gnu.org Reporter: roland.illig at gmx dot de CC: egallager at gcc dot gnu.org Target Milestone: --- Target: nvptx >From nvptx.cc: > PTX version (-mptx) needs to be at least %s to support selected -misa (sm_%s) Missing %<...%> around -mptx and -misa.
[Bug target/104903] New: missing quotes in diagnostic
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=104903 Bug ID: 104903 Summary: missing quotes in diagnostic Product: gcc Version: 12.0 Status: UNCONFIRMED Keywords: diagnostic Severity: normal Priority: P3 Component: target Assignee: unassigned at gcc dot gnu.org Reporter: roland.illig at gmx dot de CC: egallager at gcc dot gnu.org Target Milestone: --- Target: rs6000 >From rs6000-c.cc: > passing argument %d of %qE discards const qualifier from pointer target type The word "const" should be in % quotes.
[Bug target/104904] New: misplaced quotes in diagnostic
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=104904 Bug ID: 104904 Summary: misplaced quotes in diagnostic Product: gcc Version: 12.0 Status: UNCONFIRMED Keywords: diagnostic Severity: normal Priority: P3 Component: target Assignee: unassigned at gcc dot gnu.org Reporter: roland.illig at gmx dot de CC: egallager at gcc dot gnu.org, msebor at gcc dot gnu.org Target Milestone: --- Target: v850 >From v850-c.cc: > %<#pragma%> GHS end found without previous startXXX > %<#pragma%> GHS endXXX does not match previous startXXX > junk at end of %<#pragma%> ghs section > malformed %<#pragma%> ghs section > and so on Should be %<#pragma GHS endXXX%> (only 3 X, not 4 X), as well as %. Looks like a fallout from enclosing keywords in quotes, missed in the manual review.
[Bug c++/104905] New: untranslated word in diagnostic about compiled module
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=104905 Bug ID: 104905 Summary: untranslated word in diagnostic about compiled module Product: gcc Version: 12.0 Status: UNCONFIRMED Keywords: diagnostic Severity: normal Priority: P3 Component: c++ Assignee: unassigned at gcc dot gnu.org Reporter: roland.illig at gmx dot de CC: egallager at gcc dot gnu.org Target Milestone: --- >From cp/module.cc: > error_at (loc, "compiled module is %sversion %s", > IS_EXPERIMENTAL (their_ver) ? "experimental " : "", > their_string); The word "experimental" must be translatable into other languages such as German, French, Russian; currently it isn't. Fixing this properly requires to split this message into 2 separate messages since the word "experimental" alone is too ambiguous to translate without further context.
[Bug target/104253] libgcc missing __floatdiif
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=104253 Eric Botcazou changed: What|Removed |Added CC||ebotcazou at gcc dot gnu.org --- Comment #17 from Eric Botcazou --- The test fails on VxWorks, where there is no 128-bit long double: cc1: warning: The '-mfloat128' option may not be fully supported so it looks like a DejaGNU selector is missing.
[Bug target/104890] [12 Regression] fails to build the 32bit libgcc on x86_64-linux-gnu (--enable-cet --with-arch-32=i686)
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=104890 H.J. Lu changed: What|Removed |Added Attachment #52619|0 |1 is obsolete|| --- Comment #9 from H.J. Lu --- Created attachment 52620 --> https://gcc.gnu.org/bugzilla/attachment.cgi?id=52620&action=edit The v2 patch Please try the v2 patch.
[Bug c++/104906] New: UTF-8 bytes output in diagnostic regardless of locale
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=104906 Bug ID: 104906 Summary: UTF-8 bytes output in diagnostic regardless of locale Product: gcc Version: 12.0 Status: UNCONFIRMED Keywords: diagnostic Severity: normal Priority: P3 Component: c++ Assignee: unassigned at gcc dot gnu.org Reporter: roland.illig at gmx dot de CC: egallager at gcc dot gnu.org Target Milestone: --- >From cp/module.cc: inform (loc, "compiler is %sversion %s%s%s", IS_EXPERIMENTAL (my_ver) ? "experimental " : "", my_string, reject_p ? "" : flag_module_version_ignore ? ", be it on your own head!" : ", close enough?", reject_p ? "" : " \xc2\xaf\\_(\xe3\x83\x84)_/\xc2\xaf"); Are you sure that you want to output this UTF-8 sequence in locale "C"? Furthermore, the conditional strings must be translatable. See the GCC diagnostics guidelines for more information. What would happen if this diagnostic were printed in an EBCDIC environment? Might the UTF-8 sequence "\xe3\x83\x84" show up as "Tcd" there?
[Bug c++/104907] New: unclear diagnostic for fatal error
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=104907 Bug ID: 104907 Summary: unclear diagnostic for fatal error Product: gcc Version: 12.0 Status: UNCONFIRMED Keywords: diagnostic Severity: normal Priority: P3 Component: c++ Assignee: unassigned at gcc dot gnu.org Reporter: roland.illig at gmx dot de CC: egallager at gcc dot gnu.org Target Milestone: --- >From cp/module.cc: > returning to the gate for a mechanical issue This diagnostic is a fatal error. Fatal errors must be actionable. This diagnostic isn't actionable, instead it increases confusion for no reason. As a general rule, don't try to be funny if the GCC user is having a problem right now and is already mad at you.
[Bug translation/104552] Mistakes in strings to be translated in GCC 12
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=104552 Roland Illig changed: What|Removed |Added Status|NEW |RESOLVED Resolution|--- |MOVED --- Comment #40 from Roland Illig --- I have split all remaining issues from this bug report into separate bug reports: https://gcc.gnu.org/bugzilla/show_bug.cgi?id=104896 https://gcc.gnu.org/bugzilla/show_bug.cgi?id=104897 https://gcc.gnu.org/bugzilla/show_bug.cgi?id=104898 https://gcc.gnu.org/bugzilla/show_bug.cgi?id=104899 https://gcc.gnu.org/bugzilla/show_bug.cgi?id=104902 https://gcc.gnu.org/bugzilla/show_bug.cgi?id=104903 https://gcc.gnu.org/bugzilla/show_bug.cgi?id=104904 https://gcc.gnu.org/bugzilla/show_bug.cgi?id=104905 https://gcc.gnu.org/bugzilla/show_bug.cgi?id=104906 https://gcc.gnu.org/bugzilla/show_bug.cgi?id=104907
[Bug translation/40883] [meta-bug] Translation breakage with trivial fixes
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=40883 Bug 40883 depends on bug 104552, which changed state. Bug 104552 Summary: Mistakes in strings to be translated in GCC 12 https://gcc.gnu.org/bugzilla/show_bug.cgi?id=104552 What|Removed |Added Status|NEW |RESOLVED Resolution|--- |MOVED
[Bug c++/77465] [DR909] rejected C-style cast involving casting away constness from result of conversion operator
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=77465 --- Comment #4 from Ed Catmur --- Branch: https://github.com/gcc-mirror/gcc/compare/master...ecatmur:so-66816741
[Bug c++/70536] g++ doesn't emit DW_AT_name for DW_TAG_GNU_formal_parameter_pack
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=70536 --- Comment #4 from Ed Catmur --- Posted: https://gcc.gnu.org/pipermail/gcc-patches/2022-March/591678.html
[Bug fortran/104811] maxloc/minloc cannot accept character arguments without `dim` optional argument.
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=104811 --- Comment #7 from CVS Commits --- The releases/gcc-11 branch has been updated by Harald Anlauf : https://gcc.gnu.org/g:47f89da89eb0ddc9ed87192886ff633a790fe08c commit r11-9652-g47f89da89eb0ddc9ed87192886ff633a790fe08c Author: Harald Anlauf Date: Tue Mar 8 21:47:04 2022 +0100 Fortran: do not frontend-optimize MINLOC/MAXLOC for character arrays gcc/fortran/ChangeLog: PR fortran/104811 * frontend-passes.c (optimize_minmaxloc): Do not attempt frontend-optimization of MINLOC/MAXLOC for character arrays, as there is no suitable code yet for inline expansion. gcc/testsuite/ChangeLog: PR fortran/104811 * gfortran.dg/minmaxloc_16.f90: New test. (cherry picked from commit e3e369dad6cbecb1b490b3f3b154c600fba5a6f3)
[Bug fortran/104811] maxloc/minloc cannot accept character arguments without `dim` optional argument.
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=104811 anlauf at gcc dot gnu.org changed: What|Removed |Added Target Milestone|--- |11.3 --- Comment #8 from anlauf at gcc dot gnu.org --- Fixed on mainline for gcc-12, and backported to 11-branch. Closing. Thanks for the report!
[Bug fortran/104811] maxloc/minloc cannot accept character arguments without `dim` optional argument.
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=104811 anlauf at gcc dot gnu.org changed: What|Removed |Added Status|NEW |RESOLVED Resolution|--- |FIXED --- Comment #9 from anlauf at gcc dot gnu.org --- Really closing.
[Bug fortran/104908] New: gfortran 11/trunk regression: incorrect Fortran out-of-bound runtime error.
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=104908 Bug ID: 104908 Summary: gfortran 11/trunk regression: incorrect Fortran out-of-bound runtime error. Product: gcc Version: 11.2.0 Status: UNCONFIRMED Severity: normal Priority: P3 Component: fortran Assignee: unassigned at gcc dot gnu.org Reporter: a.shahmoradi at gmail dot com Target Milestone: --- The following code appears to be standard-conforming, but gfortran throws a runtime error with the flag `-check=bounds`, ``` program test type vec integer :: x(3) end type type(vec) :: v(2) call sub(v) contains subroutine sub (v) class(vec), intent(in) :: v(:) integer :: k, q(3) q = [ (v(1)%x(k), k = 1, 3) ] ! <-- fails here end subroutine end program ``` Here is the error message, ``` At line 19 of file /app/example.f90 Fortran runtime error: Index '3' of dimension 1 of array 'v%_data%x' above upper bound of 2 ``` This is a gfortran-11 regression since the code is functional with gfortran-10 with the same compile flags. It can be tested here with different versions of gfortran: https://godbolt.org/z/K6chcYE5e This issue was raised in a StackOverflow question: https://stackoverflow.com/questions/71441100/class-dummy-argument-for-array-of-custom-types-stuck-on-fcheck-bounds I am only reporting it to the GNU Bugzilla.
[Bug target/104666] [12 Regression] ICE in related_vector_mode, at stor-layout.c:537
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=104666 --- Comment #7 from CVS Commits --- The master branch has been updated by hongtao Liu : https://gcc.gnu.org/g:823b3b79cd2b137f1023742ee1ba93e8712cef0a commit r12-7638-g823b3b79cd2b137f1023742ee1ba93e8712cef0a Author: liuhongt Date: Thu Feb 24 14:42:14 2022 +0800 Don't fold builtin into gimple when isa mismatches. The patch fixes ICE in ix86_gimple_fold_builtin. gcc/ChangeLog: PR target/104666 * config/i386/i386-expand.cc (ix86_check_builtin_isa_match): New func. (ix86_expand_builtin): Move code to ix86_check_builtin_isa_match and call it. * config/i386/i386-protos.h (ix86_check_builtin_isa_match): Declare. * config/i386/i386.cc (ix86_gimple_fold_builtin): Don't fold builtin into gimple when isa mismatches. gcc/testsuite/ChangeLog: * gcc.target/i386/pr104666.c: New test.
[Bug target/104666] [12 Regression] ICE in related_vector_mode, at stor-layout.c:537
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=104666 --- Comment #8 from Hongtao.liu --- Fixed in GCC12.
[Bug target/104890] [12 Regression] fails to build the 32bit libgcc on x86_64-linux-gnu (--enable-cet --with-arch-32=i686)
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=104890 Matthias Klose changed: What|Removed |Added Status|WAITING |NEW --- Comment #10 from Matthias Klose --- The v2 patch fixes the issue for me.
[Bug target/104879] [nvptx] Use .common directive (available starting ptx isa version 5.0)
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=104879 Andrew Pinski changed: What|Removed |Added Keywords||missed-optimization --- Comment #1 from Andrew Pinski --- flag_no_common is already set by default to true since r10-4867-g6271dd984d7f92 so this is even less important than before ...
[Bug target/104882] [12 Regression] MVE: Wrong code at -O2 since r12-1434-g046a3beb1673bf4a61c131373b6a5e84158e92bf
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=104882 Andrew Pinski changed: What|Removed |Added Target Milestone|--- |12.0
[Bug c++/104837] tree check fail: in tree_operand_check, at tree.h:3948
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=104837 --- Comment #1 from Andrew Pinski --- It didn't ICE in 4.6.4 but I don't know if that is because 4.6.x didn't implement all of the C++11 features.
