[Bug rtl-optimization/92637] runtime issue with -ftree-coalesce-vars

2019-11-23 Thread pinskia at gcc dot gnu.org
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=92637 --- Comment #1 from Andrew Pinski --- > 214: aa0a03e0mov x0, x10 // HERE x10 is overwriten > by glibc Hmm, GCC knows that find_next_zero_bit will not clobber x10 so it uses across the call of that. This is due to -

[Bug tree-optimization/92618] [10 Regression] error: type mismatch in binary expression in reassoc since r273490

2019-11-23 Thread linkw at gcc dot gnu.org
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=92618 --- Comment #7 from Kewen Lin --- Sorry that I didn't catch the bugzilla mails timely, thanks for fixing this!

[Bug tree-optimization/92638] New: gcc unable to remove empty loop after loop body is removed

2019-11-23 Thread hiraditya at msn dot com
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=92638 Bug ID: 92638 Summary: gcc unable to remove empty loop after loop body is removed Product: gcc Version: 10.0 Status: UNCONFIRMED Severity: normal Prio

[Bug tree-optimization/92638] gcc unable to remove empty loop after loop body is removed

2019-11-23 Thread hiraditya at msn dot com
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=92638 --- Comment #1 from AK --- FYI: clang -O3 optimizes the empty loop.

[Bug tree-optimization/92638] gcc unable to remove empty loop after loop body is removed after malloc/free pair was removed

2019-11-23 Thread pinskia at gcc dot gnu.org
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=92638 Andrew Pinski changed: What|Removed |Added Keywords||missed-optimization Status|U

[Bug rtl-optimization/92610] [10 Regression] ICE in calc_dfs_tree, at dominance.c:458 since r270940

2019-11-23 Thread jakub at gcc dot gnu.org
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=92610 --- Comment #3 from Jakub Jelinek --- Author: jakub Date: Sat Nov 23 10:05:31 2019 New Revision: 278640 URL: https://gcc.gnu.org/viewcvs?rev=278640&root=gcc&view=rev Log: PR rtl-optimization/92610 * cse.c (rest_of_handle_cse2): C

[Bug middle-end/83859] Please add new attribute which will establish relation between parameters for buffer and its size

2019-11-23 Thread jakub at gcc dot gnu.org
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=83859 --- Comment #12 from Jakub Jelinek --- Author: jakub Date: Sat Nov 23 10:06:26 2019 New Revision: 278641 URL: https://gcc.gnu.org/viewcvs?rev=278641&root=gcc&view=rev Log: PR middle-end/83859 * doc/extend.texi (attribute access):

[Bug inline-asm/92615] [8/9/10 Regression] ICE in extract_insn

2019-11-23 Thread jakub at gcc dot gnu.org
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=92615 --- Comment #3 from Jakub Jelinek --- Author: jakub Date: Sat Nov 23 10:07:21 2019 New Revision: 278642 URL: https://gcc.gnu.org/viewcvs?rev=278642&root=gcc&view=rev Log: PR target/92615 * config/i386/i386.c (ix86_md_asm_adjust):

[Bug inline-asm/92615] [8/9 Regression] ICE in extract_insn

2019-11-23 Thread jakub at gcc dot gnu.org
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=92615 Jakub Jelinek changed: What|Removed |Added Summary|[8/9/10 Regression] ICE in |[8/9 Regression] ICE in

[Bug rtl-optimization/92610] [10 Regression] ICE in calc_dfs_tree, at dominance.c:458 since r270940

2019-11-23 Thread jakub at gcc dot gnu.org
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=92610 Jakub Jelinek changed: What|Removed |Added Status|ASSIGNED|RESOLVED Resolution|---

[Bug sanitizer/92634] [8/9/10 regression] -fsanitize=undefined erroneous null pointer check

2019-11-23 Thread amodra at gmail dot com
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=92634 --- Comment #11 from Alan Modra --- Oh wow, so the line of reasoning relies on what the C standard *doesn't* say in 6.5.3.2. I also think the deductions are somewhat suspect. You say &p->f is the same as &((*p).f), which is from p->f being the

[Bug c++/90926] [8/9/10 Regression] member char array with string literal initializer causes = {} to fail

2019-11-23 Thread jakub at gcc dot gnu.org
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=90926 Jakub Jelinek changed: What|Removed |Added CC||jakub at gcc dot gnu.org --- Comment #3

[Bug libfortran/92569] [8/9/10 Regression] gfortran read with end directive does not trigger with -ffrontend-optimize

2019-11-23 Thread tkoenig at gcc dot gnu.org
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=92569 Thomas Koenig changed: What|Removed |Added Status|NEW |ASSIGNED Assignee|unassigned a

[Bug c++/92636] out-of-class definition of member template of specialization

2019-11-23 Thread nathan at gcc dot gnu.org
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=92636 Nathan Sidwell changed: What|Removed |Added Status|UNCONFIRMED |RESOLVED Resolution|---

[Bug c++/85861] g++ -Wconversion misses int to size_t

2019-11-23 Thread jg at jguk dot org
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=85861 --- Comment #13 from Jonny Grant --- (In reply to Jonathan Wakely from comment #11) > My guess is that we don't want to warn about conversions that are > well-defined and the original value can be obtained by a round-trip. > Converting a size_t t

[Bug c++/85861] g++ -Wconversion misses int to size_t

2019-11-23 Thread jg at jguk dot org
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=85861 --- Comment #14 from Jonny Grant --- It would be useful to see the size in bits of each conversion, could that be added? Currently it shows: $ g++-8 -Wall -Wextra -Wsign-conversion -o size_t size_t.cpp size_t.cpp: In function ‘int main()’: siz

[Bug rtl-optimization/92637] runtime issue with -ftree-coalesce-vars

2019-11-23 Thread wilco at gcc dot gnu.org
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=92637 Wilco changed: What|Removed |Added CC||wilco at gcc dot gnu.org --- Comment #2 from Wil

[Bug fortran/92422] [9 Regression] Warning with character and optimisation flags

2019-11-23 Thread tkoenig at gcc dot gnu.org
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=92422 Thomas Koenig changed: What|Removed |Added Status|UNCONFIRMED |NEW Last reconfirmed|

[Bug debug/92442] Compiling Boost.Spirit.X3 code uses exuberant amount of RAM with -gpubnames

2019-11-23 Thread tkoenig at gcc dot gnu.org
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=92442 --- Comment #6 from Thomas Koenig --- Author: tkoenig Date: Sat Nov 23 15:19:19 2019 New Revision: 278647 URL: https://gcc.gnu.org/viewcvs?rev=278647&root=gcc&view=rev Log: Add test case for PR 92442. 2019-11-23 Thomas Koenig PR for

[Bug debug/92442] Compiling Boost.Spirit.X3 code uses exuberant amount of RAM with -gpubnames

2019-11-23 Thread tkoenig at gcc dot gnu.org
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=92442 Thomas Koenig changed: What|Removed |Added CC||tkoenig at gcc dot gnu.org --- Comment #

A Poster Maker For Your School

2019-11-23 Thread Poster Studio
Can't see this email?. View in browser

[Bug fortran/92639] New: Error: Integer too big for its kind at (1)

2019-11-23 Thread gsocshubham at gmail dot com
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=92639 Bug ID: 92639 Summary: Error: Integer too big for its kind at (1) Product: gcc Version: unknown Status: UNCONFIRMED Severity: normal Priority: P3 Component: fort

[Bug fortran/92639] Error: Integer too big for its kind at (1)

2019-11-23 Thread kargl at gcc dot gnu.org
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=92639 kargl at gcc dot gnu.org changed: What|Removed |Added Status|UNCONFIRMED |RESOLVED CC|

gcc-bugs@gcc.gnu.org

2019-11-23 Thread jorrit at jorrit dot de
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=92640 Bug ID: 92640 Summary: Incorrect warning: exception of type 'const derived&' will be caught by earlier handler for 'const base&' Product: gcc Version: 10.0 Status: UNCONF

[Bug c++/69373] GCC emits incorrect warning that "exception of type ‘void (*)()’ will be caught by earlier handler for 'void*'"

2019-11-23 Thread jorrit at jorrit dot de
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=69373 Jö changed: What|Removed |Added CC||jorrit at jorrit dot de --- Comment #1 from Jö ---

[Bug ipa/91832] [10 Regression] ICE in scan_expr_access, at ipa-sra.c:1695 since r275982

2019-11-23 Thread jamborm at gcc dot gnu.org
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=91832 Martin Jambor changed: What|Removed |Added Status|ASSIGNED|RESOLVED Resolution|---

[Bug c++/61414] enum class bitfield size-checking needs a separate warning flag controlling it

2019-11-23 Thread kokuam at hotmail dot com
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=61414 Alexander Kokushkin changed: What|Removed |Added CC||kokuam at hotmail dot com --- Comm

[Bug middle-end/92641] New: Function called from dead branch

2019-11-23 Thread sagebar at web dot de
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=92641 Bug ID: 92641 Summary: Function called from dead branch Product: gcc Version: 9.1.0 Status: UNCONFIRMED Severity: normal Priority: P3 Component: middle-end

[Bug c++/92641] VLA type finalized at the beginging of the statement rather at the point of use

2019-11-23 Thread pinskia at gcc dot gnu.org
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=92641 Andrew Pinski changed: What|Removed |Added Component|middle-end |c++ Summary|Function called f

[Bug libfortran/92569] [8/9/10 Regression] gfortran read with end directive does not trigger with -ffrontend-optimize

2019-11-23 Thread jvdelisle at gcc dot gnu.org
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=92569 --- Comment #9 from Jerry DeLisle --- (In reply to Thomas Koenig from comment #8) > Hope you don't mind if I take this. Hi Thomas, just noticed this one. I can review for you when you are ready.

[Bug c++/92641] VLA type finalized at the beginging of the statement rather at the point of use

2019-11-23 Thread sagebar at web dot de
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=92641 --- Comment #2 from sagebar at web dot de --- (In reply to Andrew Pinski from comment #1) > The big question comes, where should the VLA type be finalized, at the use > or at the beginning of the statement. > > Statement expressions create a new

[Bug c++/92642] New: Enhance shift-count-overflow output

2019-11-23 Thread jg at jguk dot org
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=92642 Bug ID: 92642 Summary: Enhance shift-count-overflow output Product: gcc Version: 10.0 Status: UNCONFIRMED Severity: normal Priority: P3 Component: c++

[Bug fortran/92643] New: ISO_Fortran_binding_15.f90 failure on i586-*-freebsd

2019-11-23 Thread kargl at gcc dot gnu.org
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=92643 Bug ID: 92643 Summary: ISO_Fortran_binding_15.f90 failure on i586-*-freebsd Product: gcc Version: 10.0 Status: UNCONFIRMED Severity: normal Priority: P3 Componen

[Bug fortran/92643] ISO_Fortran_binding_15.f90 failure on i586-*-freebsd

2019-11-23 Thread kargl at gcc dot gnu.org
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=92643 --- Comment #1 from kargl at gcc dot gnu.org --- Copying ISO_Fortran_binding_15.c and ISO_Fortran_binding_15.f90 to /tmp. Edit ISO_Fortran_binding_15.c to find the header file. % ~/work/bin/gcc -c ISO_Fortran_binding_15.c % gfcx -o z ISO_Fortran

[Bug tree-optimization/92644] New: [9/10 Regression] ICE in wide_int_to_tree_1, at tree.c:1530

2019-11-23 Thread asolokha at gmx dot com
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=92644 Bug ID: 92644 Summary: [9/10 Regression] ICE in wide_int_to_tree_1, at tree.c:1530 Product: gcc Version: 10.0 Status: UNCONFIRMED Severity: normal Pri

[Bug c++/69864] Fix various Wnarrowing minor issues

2019-11-23 Thread egallager at gcc dot gnu.org
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=69864 --- Comment #15 from Eric Gallager --- (In reply to Manuel López-Ibáñez from comment #8) [...snip...] > and replace the kludge in cp/typeck2.c with it (possibly fixing PR69872 > along the way). Document when some warnings might be errors (like we

[Bug libfortran/92100] Formatted stream IO irreproducible read with binary data in file

2019-11-23 Thread jvdelisle at gcc dot gnu.org
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=92100 Jerry DeLisle changed: What|Removed |Added Assignee|unassigned at gcc dot gnu.org |jvdelisle at gcc dot gnu.org ---