[Bug bootstrap/107739] --enable-languages= duplicates yield odd error

2022-11-17 Thread schwab--- via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=107739 --- Comment #4 from Andreas Schwab --- missing_languages=`echo "$missing_languages" | sed -e ':loop' -e "s/,$language,/,/" -e 't loop'`

[Bug c++/107128] armhf: floatn-common.h:214:9: error: multiple types in one declaration

2022-11-17 Thread jakub at gcc dot gnu.org via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=107128 --- Comment #9 from Jakub Jelinek --- (In reply to Mike Hommey from comment #7) > Forget my last comment, it came from the use of a sysroot with an older > glibc. I wonder why the sysroot path didn't appear in those messages... You need to use

[Bug tree-optimization/107647] [12 Regression] GCC 12.2.0 may produce FMAs even with -ffp-contract=off

2022-11-17 Thread rguenth at gcc dot gnu.org via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=107647 Richard Biener changed: What|Removed |Added Summary|[12/13 Regression] GCC |[12 Regression] GCC 12.2.0

[Bug tree-optimization/107647] [12/13 Regression] GCC 12.2.0 may produce FMAs even with -ffp-contract=off

2022-11-17 Thread cvs-commit at gcc dot gnu.org via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=107647 --- Comment #17 from CVS Commits --- The master branch has been updated by Richard Biener : https://gcc.gnu.org/g:c5df8392c5848c0462558f41cdf6eab31db301cf commit r13-4137-gc5df8392c5848c0462558f41cdf6eab31db301cf Author: Richard Biener Date:

[Bug c++/107744] New: Error in constant evaluation of dynamic_cast

2022-11-17 Thread fchelnokov at gmail dot com via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=107744 Bug ID: 107744 Summary: Error in constant evaluation of dynamic_cast Product: gcc Version: 12.2.1 Status: UNCONFIRMED Severity: normal Priority: P3 Component: c

[Bug middle-end/107743] New: expmed: extract_bit_field_1: maybe-uninitialized warning

2022-11-17 Thread aldot at gcc dot gnu.org via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=107743 Bug ID: 107743 Summary: expmed: extract_bit_field_1: maybe-uninitialized warning Product: gcc Version: 13.0 Status: UNCONFIRMED Severity: normal Prio

[Bug target/107692] [13 regression] r13-3950-g071e428c24ee8c breaks many test cases

2022-11-17 Thread wwwhhhyyy333 at gmail dot com via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=107692 --- Comment #6 from Hongyu Wang --- (In reply to Jiu Fu Guo from comment #4) > (In reply to Hongyu Wang from comment #2) > > Created attachment 53897 [details] > > A patch > > > > Sorry for introducing these fails. Here is the patch. > > > > I

[Bug target/107713] Wrong implementation atomic_exchange on LoongArch

2022-11-17 Thread cvs-commit at gcc dot gnu.org via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=107713 --- Comment #5 from CVS Commits --- The master branch has been updated by LuluCheng : https://gcc.gnu.org/g:f0024bfb228f94e60e06dc32a4983e40a9b90be5 commit r13-4136-gf0024bfb228f94e60e06dc32a4983e40a9b90be5 Author: Jinyang He Date: Thu Nov

[Bug target/107692] [13 regression] r13-3950-g071e428c24ee8c breaks many test cases

2022-11-17 Thread guojiufu at gcc dot gnu.org via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=107692 --- Comment #5 from Jiu Fu Guo --- > -munroll-only-small-loops does not turn on or off -funroll-loops, and it > should not, so that it does what it says, if nothing else. Yes, and -funroll-loops would win over -munroll-only-small-loops

[Bug target/107692] [13 regression] r13-3950-g071e428c24ee8c breaks many test cases

2022-11-17 Thread guojiufu at gcc dot gnu.org via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=107692 Jiu Fu Guo changed: What|Removed |Added CC||guojiufu at gcc dot gnu.org --- Comment #4

[Bug middle-end/14840] fold tree_code_type[CST] and tree_code_length[CST] in GCC itself

2022-11-17 Thread pinskia at gcc dot gnu.org via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=14840 --- Comment #15 from Andrew Pinski --- Looking at the -fdump-tree-optimized for generic-match.cc (-O2 -g) in terms of lines, we get: 832068 before 718872 after That is 17% less lines. That is nice improvments. Majority is debugging info for

[Bug middle-end/14840] fold tree_code_type[CST] and tree_code_length[CST] in GCC itself

2022-11-17 Thread pinskia at gcc dot gnu.org via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=14840 --- Comment #14 from Andrew Pinski --- Compile time using the same base compiler (without the patch and with --enable-checking=yes) Without the patch: apinski@xeond:~/src/upstream-gcc/gcc/objdir/gcc$ time make -j16 generic-match.o CXXFLAGS="-O2

[Bug middle-end/14840] fold tree_code_type[CST] and tree_code_length[CST] in GCC itself

2022-11-17 Thread pinskia at gcc dot gnu.org via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=14840 Andrew Pinski changed: What|Removed |Added Attachment #8839|0 |1 is obsolete|

[Bug driver/45749] Response file unwrapped between collect2.exe and ld.exe

2022-11-17 Thread pinskia at gcc dot gnu.org via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=45749 Andrew Pinski changed: What|Removed |Added Assignee|pinskia at gcc dot gnu.org |unassigned at gcc dot gnu.org

[Bug bootstrap/107739] --enable-languages= duplicates yield odd error

2022-11-17 Thread pinskia at gcc dot gnu.org via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=107739 --- Comment #3 from Andrew Pinski --- So there are two issues but I don't know how to solve the second part of the issue. The first issue is there is a missing g for the flags of the s command of the sed command here: missing_languages=`echo "$

[Bug bootstrap/107739] --enable-languages= duplicates yield odd error

2022-11-17 Thread pinskia at gcc dot gnu.org via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=107739 Andrew Pinski changed: What|Removed |Added Keywords||build, diagnostic Status|UN

[Bug c++/107128] armhf: floatn-common.h:214:9: error: multiple types in one declaration

2022-11-17 Thread pinskia at gcc dot gnu.org via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=107128 --- Comment #8 from Andrew Pinski --- (In reply to Mike Hommey from comment #7) > Forget my last comment, it came from the use of a sysroot with an older > glibc. I wonder why the sysroot path didn't appear in those messages... Can you file a n

[Bug c++/107128] armhf: floatn-common.h:214:9: error: multiple types in one declaration

2022-11-17 Thread mh+gcc at glandium dot org via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=107128 --- Comment #7 from Mike Hommey --- Forget my last comment, it came from the use of a sysroot with an older glibc. I wonder why the sysroot path didn't appear in those messages...

[Bug fortran/107742] New: class mismatch in passed procedure

2022-11-17 Thread jwmwalrus at gmail dot com via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=107742 Bug ID: 107742 Summary: class mismatch in passed procedure Product: gcc Version: 12.2.0 Status: UNCONFIRMED Severity: normal Priority: P3 Component: fortran

[Bug c++/107128] armhf: floatn-common.h:214:9: error: multiple types in one declaration

2022-11-17 Thread mh+gcc at glandium dot org via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=107128 Mike Hommey changed: What|Removed |Added CC||mh+gcc at glandium dot org --- Comment #6

[Bug c++/107741] Missed member variable name in mangling of externally visible lambdas used in inline initialization of static members

2022-11-17 Thread dblaikie at gmail dot com via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=107741 --- Comment #1 from David Blaikie --- Oh, some context - discovered while investigating a related clang bug: https://github.com/llvm/llvm-project/issues/58819 - so don't check clang for an example of what's right here, it has different bugs, tho

[Bug c++/107741] New: Missed member variable name in mangling of externally visible lambdas used in inline initialization of static members

2022-11-17 Thread dblaikie at gmail dot com via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=107741 Bug ID: 107741 Summary: Missed member variable name in mangling of externally visible lambdas used in inline initialization of static members Product: gcc Versio

[Bug c++/104066] "constinit extern long (*const f) ();" doesn't compile: gcc thinks "constinit" applies to return value, not to function pointer itself

2022-11-17 Thread pinskia at gcc dot gnu.org via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=104066 Andrew Pinski changed: What|Removed |Added Target Milestone|--- |10.5 Known to fail|

[Bug c++/107735] Inconsistent error messages for std::array out of bound due to taking the address of one-past-the-end is valid

2022-11-17 Thread pinskia at gcc dot gnu.org via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=107735 --- Comment #4 from Andrew Pinski --- (In reply to Jonathan Wakely from comment #3) > (In reply to Andrew Pinski from comment #2) > > I wonder if this is because doing > > constexpr const int *v1 = &array[3]; > > > > is valid and well defined.

[Bug c++/104066] "constinit extern long (*const f) ();" doesn't compile: gcc thinks "constinit" applies to return value, not to function pointer itself

2022-11-17 Thread mpolacek at gcc dot gnu.org via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=104066 Marek Polacek changed: What|Removed |Added Status|ASSIGNED|RESOLVED Resolution|---

[Bug c++/104066] "constinit extern long (*const f) ();" doesn't compile: gcc thinks "constinit" applies to return value, not to function pointer itself

2022-11-17 Thread cvs-commit at gcc dot gnu.org via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=104066 --- Comment #7 from CVS Commits --- The releases/gcc-10 branch has been updated by Marek Polacek : https://gcc.gnu.org/g:b9b78b4de3c7dcc6868c4af831b2d213fda21b04 commit r10-11087-gb9b78b4de3c7dcc6868c4af831b2d213fda21b04 Author: Marek Polacek

[Bug c++/107735] Inconsistent error messages for std::array out of bound due to taking the address of one-past-the-end is valid

2022-11-17 Thread redi at gcc dot gnu.org via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=107735 --- Comment #3 from Jonathan Wakely --- (In reply to Andrew Pinski from comment #2) > I wonder if this is because doing > constexpr const int *v1 = &array[3]; > > is valid and well defined. It's not, but &array.data()[3] is. I agree that's p

[Bug c++/104066] "constinit extern long (*const f) ();" doesn't compile: gcc thinks "constinit" applies to return value, not to function pointer itself

2022-11-17 Thread cvs-commit at gcc dot gnu.org via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=104066 --- Comment #6 from CVS Commits --- The releases/gcc-11 branch has been updated by Marek Polacek : https://gcc.gnu.org/g:90824f6c57e1ac7b94c558b4c99721b412df75ef commit r11-10381-g90824f6c57e1ac7b94c558b4c99721b412df75ef Author: Marek Polacek

[Bug c++/104066] "constinit extern long (*const f) ();" doesn't compile: gcc thinks "constinit" applies to return value, not to function pointer itself

2022-11-17 Thread cvs-commit at gcc dot gnu.org via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=104066 --- Comment #5 from CVS Commits --- The releases/gcc-12 branch has been updated by Marek Polacek : https://gcc.gnu.org/g:14faa5f585f6025df1e04c8c8b34340ff5e4d494 commit r12-8916-g14faa5f585f6025df1e04c8c8b34340ff5e4d494 Author: Marek Polacek

[Bug c++/104066] "constinit extern long (*const f) ();" doesn't compile: gcc thinks "constinit" applies to return value, not to function pointer itself

2022-11-17 Thread cvs-commit at gcc dot gnu.org via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=104066 --- Comment #4 from CVS Commits --- The trunk branch has been updated by Marek Polacek : https://gcc.gnu.org/g:7b3b2f50953c5143d4b14b59d322d8a793f411dd commit r13-4135-g7b3b2f50953c5143d4b14b59d322d8a793f411dd Author: Marek Polacek Date: Th

[Bug middle-end/107737] seemly looking off code in gimplify_call_expr

2022-11-17 Thread pinskia at gcc dot gnu.org via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=107737 Andrew Pinski changed: What|Removed |Added Status|NEW |ASSIGNED

[Bug middle-end/107737] seemly looking off code in gimplify_call_expr

2022-11-17 Thread pinskia at gcc dot gnu.org via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=107737 Andrew Pinski changed: What|Removed |Added Ever confirmed|0 |1 Status|UNCONFIRMED

[Bug bootstrap/107739] --enable-languages= duplicates yield odd error

2022-11-17 Thread pinskia at gcc dot gnu.org via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=107739 --- Comment #1 from Andrew Pinski --- I thought this was fixed at one point.

[Bug c++/107735] Inconsistent error messages for std::array out of bound

2022-11-17 Thread pinskia at gcc dot gnu.org via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=107735 --- Comment #2 from Andrew Pinski --- I wonder if this is because doing constexpr const int *v1 = &array[3]; is valid and well defined. Even clang gives two different error messages: :3:21: error: constexpr variable 'v1' must be initialized b

[Bug fortran/107595] ICE in ix86_push_argument, at config/i386/i386.cc:4335

2022-11-17 Thread anlauf at gcc dot gnu.org via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=107595 anlauf at gcc dot gnu.org changed: What|Removed |Added CC||anlauf at gcc dot gnu.org --

[Bug target/101985] vec_cpsgn parameter order

2022-11-17 Thread mark.j.abraham at gmail dot com via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=101985 Mark Abraham changed: What|Removed |Added CC||mark.j.abraham at gmail dot com --- Comm

[Bug tree-optimization/107740] [12/13 Regression] if-to-switch conversion happens for simple predicate function when compiled with gcc but not with g++

2022-11-17 Thread pinskia at gcc dot gnu.org via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=107740 --- Comment #3 from Andrew Pinski --- >phi-opt1 is the "early phi-opt" which tries not to do it here. Let me expand on that, it tries not to insert a cast here to do the conversion from bool to int.

[Bug tree-optimization/107740] [12/13 Regression] if-to-switch conversion happens for simple predicate function when compiled with gcc but not with g++

2022-11-17 Thread pinskia at gcc dot gnu.org via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=107740 Andrew Pinski changed: What|Removed |Added Ever confirmed|0 |1 Target Milestone|---

[Bug fortran/107576] [10/11/12/13 Regression] ICE in gfc_conv_procedure_call, at fortran/trans-expr.cc:6193

2022-11-17 Thread anlauf at gcc dot gnu.org via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=107576 anlauf at gcc dot gnu.org changed: What|Removed |Added Assignee|unassigned at gcc dot gnu.org |anlauf at gcc dot gnu

[Bug tree-optimization/107740] if-to-switch conversion happens for simple predicate function when compiled with gcc but not with g++

2022-11-17 Thread pinskia at gcc dot gnu.org via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=107740 Andrew Pinski changed: What|Removed |Added Keywords||missed-optimization --- Comment #1 from

[Bug c/107705] [12/13 Regression] ICE: tree check: expected class 'type', have 'exceptional' (error_mark) in ix86_function_type_abi, at config/i386/i386.cc:1529

2022-11-17 Thread pinskia at gcc dot gnu.org via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=107705 --- Comment #2 from Andrew Pinski --- diff --git a/gcc/function.cc b/gcc/function.cc index 361aa5f7ed1..9c8773bbc59 100644 --- a/gcc/function.cc +++ b/gcc/function.cc @@ -2090,6 +2090,9 @@ aggregate_value_p (const_tree exp, const_tree fntype)

[Bug tree-optimization/107740] New: if-to-switch conversion happens for simple predicate function when compiled with gcc but not with g++

2022-11-17 Thread ppalka at gcc dot gnu.org via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=107740 Bug ID: 107740 Summary: if-to-switch conversion happens for simple predicate function when compiled with gcc but not with g++ Product: gcc Version: 13.0 Status: UNCONFIR

[Bug middle-end/107307] [12/13 Regression] ICE tree check: expected class 'type', have 'exceptional' (error_mark) in canonicalize_component_ref, at gimplify.cc:2923 since r12-3278-g823685221de986af

2022-11-17 Thread pinskia at gcc dot gnu.org via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=107307 Andrew Pinski changed: What|Removed |Added See Also||https://gcc.gnu.org/bugzill

[Bug middle-end/107307] [12/13 Regression] ICE tree check: expected class 'type', have 'exceptional' (error_mark) in canonicalize_component_ref, at gimplify.cc:2923 since r12-3278-g823685221de986af

2022-11-17 Thread pinskia at gcc dot gnu.org via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=107307 --- Comment #2 from Andrew Pinski --- Simple fix: diff --git a/gcc/gimplify.cc b/gcc/gimplify.cc index f06ce3cc77a..bd772c15bec 100644 --- a/gcc/gimplify.cc +++ b/gcc/gimplify.cc @@ -3319,7 +3319,9 @@ gimplify_compound_lval (tree *expr_p, gimple

[Bug c/106764] [12/13 Regression] ICE on invalid code in tree check: expected function_type or method_type, have error_mark in gimplify_call_expr, at gimplify.cc

2022-11-17 Thread pinskia at gcc dot gnu.org via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=106764 --- Comment #4 from Andrew Pinski --- Actually the fix is just check the return value of gimplify_expr to make sure it was not GS_ERROR. diff --git a/gcc/gimplify.cc b/gcc/gimplify.cc index f06ce3cc77a..9b74f957308 100644 --- a/gcc/gimplify.cc

[Bug bootstrap/107739] New: --enable-languages= duplicates yield odd error

2022-11-17 Thread aldot at gcc dot gnu.org via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=107739 Bug ID: 107739 Summary: --enable-languages= duplicates yield odd error Product: gcc Version: 13.0 Status: UNCONFIRMED Severity: normal Priority: P3 Component: b

[Bug c/106764] [12/13 Regression] ICE on invalid code in tree check: expected function_type or method_type, have error_mark in gimplify_call_expr, at gimplify.cc

2022-11-17 Thread pinskia at gcc dot gnu.org via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=106764 --- Comment #3 from Andrew Pinski --- At the point where the CALL_EXPR is built: Breakpoint 5, build_function_call_vec (loc=258624, arg_loc=..., function=, params=0x0, origtypes=0x0, orig_fundecl=) at /home/apinski/src/upstream-gcc/gcc/gcc/c/c-t

[Bug middle-end/107734] [13 Regression] valgrind error for gcc/testsuite/cc.target/i386/pr46051.c

2022-11-17 Thread pinskia at gcc dot gnu.org via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=107734 --- Comment #11 from Andrew Pinski --- (In reply to David Binderman from comment #10) > (In reply to Andrew Pinski from comment #9) > > Fixed. > > Thanks for that. > > Would it ok to manually check all uses of sbitmap, to make sure they > ini

[Bug c/107736] call to a function, generated by inline asm, is off by one byte

2022-11-17 Thread pinskia at gcc dot gnu.org via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=107736 --- Comment #5 from Andrew Pinski --- (In reply to mfarca from comment #4) > Thanks for creating the issue for improving documentation. > > Could you then clarify if call to the incorrect address is a bug or not? > instructions are allowed to b

[Bug c/107738] Top-level inline-asm is not well documented

2022-11-17 Thread pinskia at gcc dot gnu.org via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=107738 --- Comment #1 from Andrew Pinski --- I know there are other related bugs where people mess up the top-level inline-asm too but I can't find them right now.

[Bug c/107736] call to a function, generated by inline asm, is off by one byte

2022-11-17 Thread miladfarca at gmail dot com via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=107736 --- Comment #4 from mfarca --- Thanks for creating the issue for improving documentation. Could you then clarify if call to the incorrect address is a bug or not? instructions are allowed to be under `.rodata` section as this section is still e

[Bug middle-end/107734] [13 Regression] valgrind error for gcc/testsuite/cc.target/i386/pr46051.c

2022-11-17 Thread dcb314 at hotmail dot com via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=107734 --- Comment #10 from David Binderman --- (In reply to Andrew Pinski from comment #9) > Fixed. Thanks for that. Would it ok to manually check all uses of sbitmap, to make sure they initialise bits appropriately, or would it be better to define

[Bug c/107736] call to a function, generated by inline asm, is off by one byte

2022-11-17 Thread pinskia at gcc dot gnu.org via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=107736 Andrew Pinski changed: What|Removed |Added See Also||https://gcc.gnu.org/bugzill

[Bug fortran/99884] Double spaces in warning message

2022-11-17 Thread cvs-commit at gcc dot gnu.org via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=99884 --- Comment #2 from CVS Commits --- The master branch has been updated by Bernhard Reutner-Fischer : https://gcc.gnu.org/g:19be89d79ee149e812ccc6027956cefb7f3e1016 commit r13-4133-g19be89d79ee149e812ccc6027956cefb7f3e1016 Author: Bernhard Reutn

[Bug c/107738] New: Top-level inline-asm is not well documented

2022-11-17 Thread pinskia at gcc dot gnu.org via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=107738 Bug ID: 107738 Summary: Top-level inline-asm is not well documented Product: gcc Version: 13.0 Status: UNCONFIRMED Keywords: documentation, inline-asm Severity: normal

[Bug c/107736] call to a function, generated by inline asm, is off by one byte

2022-11-17 Thread miladfarca at gmail dot com via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=107736 --- Comment #2 from mfarca --- > Toplevel inline-asm will be emitted without any knowledge of the current > section. So this is a limitation of gcc I guess? as clang does have the knowledge on which is which. The main issue still persists as c

[Bug c/107736] call to a function, generated by inline asm, is off by one byte

2022-11-17 Thread pinskia at gcc dot gnu.org via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=107736 Andrew Pinski changed: What|Removed |Added Resolution|--- |INVALID Keywords|

[Bug middle-end/107737] New: seemly looking off code in gimplify_call_expr

2022-11-17 Thread pinskia at gcc dot gnu.org via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=107737 Bug ID: 107737 Summary: seemly looking off code in gimplify_call_expr Product: gcc Version: 13.0 Status: UNCONFIRMED Severity: normal Priority: P3 Component: mi

[Bug c/107736] New: call to a function, generated by inline asm, is off by one byte

2022-11-17 Thread miladfarca at gmail dot com via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=107736 Bug ID: 107736 Summary: call to a function, generated by inline asm, is off by one byte Product: gcc Version: 12.2.0 Status: UNCONFIRMED Severity: normal

[Bug c++/105278] -Wliteral-range vs -Wfloat-equal

2022-11-17 Thread pinskia at gcc dot gnu.org via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=105278 --- Comment #8 from Andrew Pinski --- So clang emits one or the other warning for the code but not both. You can defect the warning in clang by doing: ``` extern void g( int); void f(float a) { double b = a; if (b == 0.1234) g( 1); } ``

[Bug middle-end/107734] [13 Regression] valgrind error for gcc/testsuite/cc.target/i386/pr46051.c

2022-11-17 Thread pinskia at gcc dot gnu.org via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=107734 Andrew Pinski changed: What|Removed |Added Status|ASSIGNED|RESOLVED Resolution|---

[Bug middle-end/107734] [13 Regression] valgrind error for gcc/testsuite/cc.target/i386/pr46051.c

2022-11-17 Thread cvs-commit at gcc dot gnu.org via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=107734 --- Comment #8 from CVS Commits --- The trunk branch has been updated by Andrew Pinski : https://gcc.gnu.org/g:ee892832ea19b21a3420ef042e582204fac852a2 commit r13-4132-gee892832ea19b21a3420ef042e582204fac852a2 Author: Andrew Pinski Date: Th

[Bug c++/107732] ICE in lower_bound, at value-range.h:350

2022-11-17 Thread aldyh at gcc dot gnu.org via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=107732 Aldy Hernandez changed: What|Removed |Added Status|NEW |RESOLVED Resolution|---

[Bug c++/107732] ICE in lower_bound, at value-range.h:350

2022-11-17 Thread cvs-commit at gcc dot gnu.org via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=107732 --- Comment #4 from CVS Commits --- The master branch has been updated by Aldy Hernandez : https://gcc.gnu.org/g:4e306222f442f8d4c6fc6da997ab756a5e43e36e commit r13-4131-g4e306222f442f8d4c6fc6da997ab756a5e43e36e Author: Aldy Hernandez Date:

[Bug middle-end/107734] [13 Regression] valgrind error for gcc/testsuite/cc.target/i386/pr46051.c

2022-11-17 Thread pinskia at gcc dot gnu.org via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=107734 Andrew Pinski changed: What|Removed |Added Summary|valgrind error for |[13 Regression] valgrind

[Bug analyzer/107711] [13 Regression] ICE with "-fanalyzer -Wunused-macros" since r13-4073-gd8aba860b34203

2022-11-17 Thread dmalcolm at gcc dot gnu.org via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=107711 David Malcolm changed: What|Removed |Added Status|WAITING |RESOLVED Resolution|---

[Bug analyzer/107711] [13 Regression] ICE with "-fanalyzer -Wunused-macros" since r13-4073-gd8aba860b34203

2022-11-17 Thread cvs-commit at gcc dot gnu.org via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=107711 --- Comment #11 from CVS Commits --- The master branch has been updated by David Malcolm : https://gcc.gnu.org/g:f9ed1d24ee46f5ca759c35a1f51fa163d7529ea6 commit r13-4130-gf9ed1d24ee46f5ca759c35a1f51fa163d7529ea6 Author: David Malcolm Date:

[Bug c/107734] valgrind error for gcc/testsuite/cc.target/i386/pr46051.c

2022-11-17 Thread dcb314 at hotmail dot com via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=107734 --- Comment #6 from David Binderman --- I am trying a bisect with git hash b4fca4fc70dc76cf.

[Bug c/107734] valgrind error for gcc/testsuite/cc.target/i386/pr46051.c

2022-11-17 Thread dcb314 at hotmail dot com via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=107734 --- Comment #5 from David Binderman --- I have reduced one of the test cases downto this code: float val1f[][2], val2f[][2], chkf[][2]; foof_i; foof() { int j; foof_i = 0; for (; foof_i < 8; foof_i++) { float tmp = val1f[foof_i][j] *

[Bug target/107515] MVE: Generic functions do not accept _Float16 scalars

2022-11-17 Thread stammark at gcc dot gnu.org via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=107515 Stam Markianos-Wright changed: What|Removed |Added Status|NEW |ASSIGNED --- Comment #3 from St

[Bug target/107714] MVE: Invalid addressing mode generated for VLD2

2022-11-17 Thread stammark at gcc dot gnu.org via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=107714 Stam Markianos-Wright changed: What|Removed |Added Last reconfirmed||2022-11-17 --- Comment #3 from

[Bug target/107604] FAIL: gcc.target/aarch64/aapcs64/test_dfp_17.c execution, -O0 fails on aarch64_be

2022-11-17 Thread clyon at gcc dot gnu.org via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=107604 --- Comment #3 from Christophe Lyon --- and patching test_dfp_17.c like so: - ANON(_Decimal32, f1, STACK+32) /* Note: no promotion to _Decimal64. */ + ANON(_Decimal32, f1, STACK+36) /* Note: no promotion to _Decimal64. */ makes it pass on aa

[Bug c++/107735] Inconsistent error messages for std::array out of bound

2022-11-17 Thread redi at gcc dot gnu.org via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=107735 Jonathan Wakely changed: What|Removed |Added Last reconfirmed||2022-11-17 Status|UNCONFI

[Bug c++/107732] ICE in lower_bound, at value-range.h:350

2022-11-17 Thread aldyh at gcc dot gnu.org via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=107732 --- Comment #3 from Aldy Hernandez --- (In reply to Andrey Alekseenko from comment #2) > @Aldy Hernandez, thank you. Can confirm that your patch fully resolves the > issue for me. No problem. Thank your for reporting and for reducing. It make

[Bug c++/107732] ICE in lower_bound, at value-range.h:350

2022-11-17 Thread gcc-bugzilla at al42and dot me via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=107732 --- Comment #2 from Andrey Alekseenko --- @Aldy Hernandez, thank you. Can confirm that your patch fully resolves the issue for me.

[Bug c++/107732] ICE in lower_bound, at value-range.h:350

2022-11-17 Thread aldyh at gcc dot gnu.org via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=107732 --- Comment #1 from Aldy Hernandez --- Created attachment 53920 --> https://gcc.gnu.org/bugzilla/attachment.cgi?id=53920&action=edit untested [PR tree-optimization/107732] [range-ops] Handle attempt to abs() negatives. The threader is creati

[Bug c++/78655] gcc doesn't exploit the fact that the result of pointer addition can not be nullptr

2022-11-17 Thread amacleod at redhat dot com via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=78655 --- Comment #18 from Andrew Macleod --- (In reply to rguent...@suse.de from comment #17) > On Thu, 17 Nov 2022, amacleod at redhat dot com wrote: > > > https://gcc.gnu.org/bugzilla/show_bug.cgi?id=78655 > > > > --- Comment #16 from Andrew Macle

[Bug tree-optimization/90134] ICE in duplicate_eh_regions_1, at except.c:557

2022-11-17 Thread asolokha at gmx dot com via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=90134 --- Comment #4 from Arseny Solokha --- (In reply to Andrew Pinski from comment #3) > This code is all undefined anyways . Yes, but what about unmodified tests from libstdc++? I occasionally hit this ICE on them too, as shown in comment 2. I'

[Bug rust/107633] [13 regression] Bootstrap failure due to -Werror=unused-parameter and -Werror=dangling-reference

2022-11-17 Thread mpolacek at gcc dot gnu.org via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=107633 Marek Polacek changed: What|Removed |Added Resolution|--- |FIXED Status|UNCONFIRMED

[Bug c++/107732] ICE in lower_bound, at value-range.h:350

2022-11-17 Thread aldyh at gcc dot gnu.org via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=107732 Aldy Hernandez changed: What|Removed |Added Last reconfirmed||2022-11-17 Ever confirmed|0

[Bug libstdc++/107735] New: Inconsistent error messages for std::array out of bound

2022-11-17 Thread andrzej at rpi dot pl via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=107735 Bug ID: 107735 Summary: Inconsistent error messages for std::array out of bound Product: gcc Version: 12.1.0 Status: UNCONFIRMED Severity: normal Pri

[Bug tree-optimization/107451] [11/12/13 Regression] Segmentation fault with vectorized code since r11-6434

2022-11-17 Thread rguenth at gcc dot gnu.org via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=107451 --- Comment #10 from Richard Biener --- Interestingly the following variant of the testcase falls back to VMAT_ELEMENTWISE but does have the same problem there fixed up by later folding, but it will segfault when using -O2 -mavx2 -fno-vect-cost-

[Bug tree-optimization/107451] [11/12/13 Regression] Segmentation fault with vectorized code since r11-6434

2022-11-17 Thread bartoldeman at users dot sourceforge.net via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=107451 --- Comment #9 from bartoldeman at users dot sourceforge.net --- I ended up using -mprefer-vector-width=128 as a workaround myself (via __attribute__((target("prefer-vector-width=128", so there is still some AVX vectorization.

[Bug tree-optimization/107451] [11/12/13 Regression] Segmentation fault with vectorized code since r11-6434

2022-11-17 Thread rguenth at gcc dot gnu.org via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=107451 --- Comment #8 from Richard Biener --- Peeling for gaps also isn't a good fix here. One could envision a case with even three iterations ahead load with for(i = 0; i < n; i++) { dot[0] += x[ix] * y[ix] ;

[Bug c++/78655] gcc doesn't exploit the fact that the result of pointer addition can not be nullptr

2022-11-17 Thread rguenther at suse dot de via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=78655 --- Comment #17 from rguenther at suse dot de --- On Thu, 17 Nov 2022, amacleod at redhat dot com wrote: > https://gcc.gnu.org/bugzilla/show_bug.cgi?id=78655 > > --- Comment #16 from Andrew Macleod --- > (In reply to rguent...@suse.de from com

[Bug c++/78655] gcc doesn't exploit the fact that the result of pointer addition can not be nullptr

2022-11-17 Thread amacleod at redhat dot com via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=78655 --- Comment #16 from Andrew Macleod --- (In reply to rguent...@suse.de from comment #15) > On Wed, 16 Nov 2022, amacleod at redhat dot com wrote: > > > https://gcc.gnu.org/bugzilla/show_bug.cgi?id=78655 > > > > Andrew Macleod changed: > > > >

[Bug target/107604] FAIL: gcc.target/aarch64/aapcs64/test_dfp_17.c execution, -O0 fails on aarch64_be

2022-11-17 Thread clyon at gcc dot gnu.org via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=107604 --- Comment #2 from Christophe Lyon --- Confirmed. In test_dfp_17.c we have: ARG(_Decimal64, 11.0dd, D0) DOTS ANON(struct z, a, D1) ANON(struct z, b, STACK) ANON(int , 5, W0) ANON(_Decimal32, f1, STACK+32) /* Note: no promotion to _D

[Bug c/107734] valgrind error for gcc/testsuite/cc.target/i386/pr46051.c

2022-11-17 Thread dcb314 at hotmail dot com via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=107734 --- Comment #4 from David Binderman --- A third: ./gcc.target/i386/pr61403.c ==749959== Conditional jump or move depends on uninitialised value(s) ==749959==at 0x11DFAE7: bitmap_set_bit (sbitmap.h:137) ==749959==by 0x11DFAE7: gimple_sim

[Bug c++/105278] -Wliteral-range vs -Wfloat-equal

2022-11-17 Thread egallager at gcc dot gnu.org via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=105278 --- Comment #7 from Eric Gallager --- (In reply to Andrew Pinski from comment #6) > I don't think clang implements -Wfloat-equal at all, at least they didn't at > the last time I looked a few years back. I just checked their diagnostics referen

[Bug tree-optimization/107647] [12/13 Regression] GCC 12.2.0 may produce FMAs even with -ffp-contract=off

2022-11-17 Thread rguenth at gcc dot gnu.org via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=107647 --- Comment #16 from Richard Biener --- (In reply to Alexander Monakov from comment #15) > I'm confused about the first hunk in the attached patch: > > --- a/gcc/tree-vect-slp-patterns.cc > +++ b/gcc/tree-vect-slp-patterns.cc > @@ -1035,8 +1035

[Bug c/107734] valgrind error for gcc/testsuite/cc.target/i386/pr46051.c

2022-11-17 Thread dcb314 at hotmail dot com via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=107734 --- Comment #3 from David Binderman --- Another test case: ./gcc.target/i386/pr53366-2.c ==41== Conditional jump or move depends on uninitialised value(s) ==41==at 0x11DFAE7: bitmap_set_bit (sbitmap.h:137) ==41==by 0x11DFAE

[Bug c/107734] valgrind error for gcc/testsuite/cc.target/i386/pr46051.c

2022-11-17 Thread dcb314 at hotmail dot com via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=107734 --- Comment #2 from David Binderman --- git blame says dc95e1e970 (Hongyu Wang 2022-01-17 13:01:51 +0800 8292)if (!bitmap_set_bit (seen, sel[i].to_constant ()))

[Bug c++/107138] [12/13 regression] std::variant triggers false-positive 'may be used uninitialized' warning

2022-11-17 Thread marco.clemencic at gmail dot com via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=107138 --- Comment #5 from Marco Clemencic --- I forgot to mention that I compiled with the options: g++ -c -Wmaybe-uninitialized -O1 -v -save-temps test.cpp

[Bug c++/107138] [12/13 regression] std::variant triggers false-positive 'may be used uninitialized' warning

2022-11-17 Thread marco.clemencic at gmail dot com via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=107138 --- Comment #4 from Marco Clemencic --- I have a similar problem with this chunk of code: ``` #include #include #include #include #include struct Wrapper { using Map = std::map; using Value = std::variant; Wrapper(Value v) : da

[Bug c/107734] valgrind error for gcc/testsuite/cc.target/i386/pr46051.c

2022-11-17 Thread dcb314 at hotmail dot com via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=107734 --- Comment #1 from David Binderman --- The valgrind problem doesn't seem to occur with git hash 05432288d4e56055, dated 20221113, so the bug is recent. I used git hash 2b2f2ee49a33419f for today's build.

[Bug c++/107138] [12/13 regression] std::variant triggers false-positive 'may be used uninitialized' warning

2022-11-17 Thread marco.clemencic at gmail dot com via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=107138 Marco Clemencic changed: What|Removed |Added CC||marco.clemencic at gmail dot com ---

[Bug c/107734] New: valgrind error for gcc/testsuite/cc.target/i386/pr46051.c

2022-11-17 Thread dcb314 at hotmail dot com via Gcc-bugs
~/gcc/results.20221117.valgrind/bin/gcc -c -O2 ./gcc.target/i386/pr46051.c ==639651== Conditional jump or move depends on uninitialised value(s) ==639651==at 0x11DFAE7: bitmap_set_bit (sbitmap.h:137) ==639651==by 0x11DFAE7: gimple_simplify_122(gimple_match_op*, gimple**, tree _node* (*)(tree

[Bug sanitizer/103930] asan intercepts fail if target library is only loaded (indirectly) through dlopen (e.g. plugin)

2022-11-17 Thread jengelh at inai dot de via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=103930 --- Comment #2 from Jan Engelhardt --- Subissue a) "the crash output is completely useless" seems to have been addressed in the past already; I observe in gcc 12 that Found plugin run function: 0x7fecaa0e01a0 AddressSanitizer:DEADLYSIGNAL =

[Bug libstdc++/107675] [13 Regression] GCC-13 is significantly slower to startup on C++ programs

2022-11-17 Thread tnfchris at gcc dot gnu.org via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=107675 --- Comment #9 from Tamar Christina --- (In reply to Florian Weimer from comment #8) > (In reply to Tamar Christina from comment #4) > > /opt/buildAgent/work/5c94c4ced6ebfcd0/libgcc/unwind-dw2-fde.c:111 > > #6 __register_frame_info (begin=, ob=

[Bug sanitizer/103930] asan intercepts fail if target library is only loaded (indirectly) through dlopen (e.g. plugin)

2022-11-17 Thread jengelh at inai dot de via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=103930 Jan Engelhardt changed: What|Removed |Added CC||rguenther at suse dot de --- Comment #

  1   2   >