[Bug tree-optimization/95295] g++ produces incorrect code with -O3 for loops

2020-06-06 Thread gsocshubham at gmail dot com
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=95295 Shubham Narlawar changed: What|Removed |Added CC||gsocshubham at gmail dot com

[Bug fortran/93522] New: f951: internal compiler error: in gfc_release_symbol, at fortran/symbol.c:3121

2020-01-30 Thread gsocshubham at gmail dot com
: normal Priority: P3 Component: fortran Assignee: unassigned at gcc dot gnu.org Reporter: gsocshubham at gmail dot com Target Milestone: --- Testcase run on godbolt compiler x86-64 gfortran (trunk) - ---Testcase

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

2019-11-23 Thread gsocshubham at gmail dot com
: fortran Assignee: unassigned at gcc dot gnu.org Reporter: gsocshubham at gmail dot com Target Milestone: --- For below testcase, I ran on godbolt.org GFORTRAN trunk. Here are some observations - gfortran throws an error for BGE intrinsic when the value of one of parameter

[Bug fortran/92629] New: internal compiler error: in convert_mpz_to_unsigned, at fortran/simplify.c:173

2019-11-22 Thread gsocshubham at gmail dot com
Severity: normal Priority: P3 Component: fortran Assignee: unassigned at gcc dot gnu.org Reporter: gsocshubham at gmail dot com Target Milestone: --- For below testcase, I ran on godbolt.org GFORTRAN trunk - TESTCASE

[Bug target/91106] internal compiler error: output_operand: invalid use of register 'frame'

2019-07-08 Thread gsocshubham at gmail dot com
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=91106 --- Comment #2 from Shubham Narlawar --- (In reply to Richard Biener from comment #1) > Did you paste the correct reduced testcase? Here is the original reduced test case obtained from Creduce - #pragma pack(1) struct a { int b; char c };

[Bug middle-end/91106] New: internal compiler error: output_operand: invalid use of register 'frame'

2019-07-07 Thread gsocshubham at gmail dot com
Priority: P3 Component: middle-end Assignee: unassigned at gcc dot gnu.org Reporter: gsocshubham at gmail dot com Target Milestone: --- Host: x86_64-linux-gnu Target: x86_64-linux-gnu Build: x86_64-linux-gnu Created

[Bug middle-end/91105] New: internal compiler error: maximum number of generated reload insns per insn achieved (90)

2019-07-07 Thread gsocshubham at gmail dot com
Severity: normal Priority: P3 Component: middle-end Assignee: unassigned at gcc dot gnu.org Reporter: gsocshubham at gmail dot com Target Milestone: --- Host: x86_64-linux-gnu Target: x86_64-linux-gnu Build: x86_64-linux

[Bug middle-end/91021] New: internal compiler error: Segmentation fault

2019-06-27 Thread gsocshubham at gmail dot com
: middle-end Assignee: unassigned at gcc dot gnu.org Reporter: gsocshubham at gmail dot com Target Milestone: --- Host: x86_64-linux-gnu Target: x86_64-linux-gnu Build: x86_64-linux-gnu Created attachment 46528 --> https://gcc.gnu.

[Bug target/91001] internal compiler error: in extract_insn, at recog.c:2310

2019-06-26 Thread gsocshubham at gmail dot com
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=91001 --- Comment #1 from Shubham Narlawar --- Below is reduced test case after fixing warning. void f(); #pragma pack(1) struct a { short b; char c; }; union{ struct a c; } __attribute__((aligned(128), transparent_union)) d; void e() { f(d);

[Bug c/91001] New: internal compiler error: in extract_insn, at recog.c:2310

2019-06-26 Thread gsocshubham at gmail dot com
Priority: P3 Component: c Assignee: unassigned at gcc dot gnu.org Reporter: gsocshubham at gmail dot com Target Milestone: --- Host: x86_64-linux-gnu Target: x86_64-linux-gnu Build: x86_64-linux-gnu Created attachment 46521

[Bug c/90071] New: internal compiler error: SSA corruption

2019-04-12 Thread gsocshubham at gmail dot com
Assignee: unassigned at gcc dot gnu.org Reporter: gsocshubham at gmail dot com CC: mliska at suse dot cz Target Milestone: --- Host: x86_64-linux-gnu Target: x86_64-linux-gnu Build: x86_64-linux-gnu Created attachment 46154

[Bug c/89737] New: internal compiler error: Floating point exception

2019-03-16 Thread gsocshubham at gmail dot com
: c Assignee: unassigned at gcc dot gnu.org Reporter: gsocshubham at gmail dot com Target Milestone: --- Host: x86_64-linux-gnu Target: x86_64-linux-gnu Build: x86_64-linux-gnu Created attachment 45980 --> https://gcc.gnu.org/bugzi

[Bug middle-end/89351] New: internal compiler error: in exact_div, at poly-int.h:2139

2019-02-14 Thread gsocshubham at gmail dot com
Priority: P3 Component: middle-end Assignee: unassigned at gcc dot gnu.org Reporter: gsocshubham at gmail dot com Target Milestone: --- Host: x86_64-linux-gnu Target: x86_64-linux-gnu Build: x86_64-linux-gnu Created attachment 45722

[Bug tree-optimization/83581] [8 Regression] ICE in expand_LOOP_VECTORIZED, at internal-fn.c:2397

2019-02-08 Thread gsocshubham at gmail dot com
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=83581 --- Comment #11 from Shubham Narlawar --- Is it ok if I send .c extension file as an attachment? On Fri, Feb 8, 2019 at 2:42 PM wrote: > Attachments with a MIME type of "text/html" are not allowed on this > installation. > > Shubham Narlawar

[Bug tree-optimization/83581] [8 Regression] ICE in expand_LOOP_VECTORIZED, at internal-fn.c:2397

2019-02-08 Thread gsocshubham at gmail dot com
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=83581 --- Comment #10 from Shubham Narlawar --- I have opened a new bug report for above. Here is the link. https://gcc.gnu.org/bugzilla/show_bug.cgi?id=89248 I attached the preprocessed code of the original program in the report. On Fri, Feb 8,

[Bug tree-optimization/89248] New: internal compiler error: in expand_LOOP_VECTORIZED, at internal-fn.c:2409

2019-02-08 Thread gsocshubham at gmail dot com
: normal Priority: P3 Component: tree-optimization Assignee: unassigned at gcc dot gnu.org Reporter: gsocshubham at gmail dot com Target Milestone: --- Host: x86_64-linux-gnu Target: x86_64-linux-gnu Build: x86_64-linux-gnu

[Bug tree-optimization/83581] [8 Regression] ICE in expand_LOOP_VECTORIZED, at internal-fn.c:2397

2019-02-07 Thread gsocshubham at gmail dot com
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=83581 --- Comment #6 from Shubham Narlawar --- Created attachment 45637 --> https://gcc.gnu.org/bugzilla/attachment.cgi?id=45637=edit Preprocessed code of file named "work23_crash1.c" internal compiler error: in expand_LOOP_VECTORIZED, at

[Bug tree-optimization/83581] [8 Regression] ICE in expand_LOOP_VECTORIZED, at internal-fn.c:2397

2019-02-07 Thread gsocshubham at gmail dot com
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=83581 Shubham Narlawar changed: What|Removed |Added CC||gsocshubham at gmail dot com

[Bug c/89153] New: internal compiler error: in assign_stack_local_1, at function.c:409

2019-02-01 Thread gsocshubham at gmail dot com
Priority: P3 Component: c Assignee: unassigned at gcc dot gnu.org Reporter: gsocshubham at gmail dot com Target Milestone: --- Host: x86_64-linux-gnu Target: x86_64-linux-gnu Build: x86_64-linux-gnu Created attachment

[Bug tree-optimization/89135] [7/8/9 Regression] internal compiler error: in gimple_split_edge, at tree-cfg.c:2747

2019-01-31 Thread gsocshubham at gmail dot com
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=89135 --- Comment #3 from Shubham Narlawar --- I could reproduce the ICE on gcc-8.2 but not on trunk.

[Bug tree-optimization/89135] New: internal compiler error: in gimple_split_edge, at tree-cfg.c:2747

2019-01-30 Thread gsocshubham at gmail dot com
Priority: P3 Component: tree-optimization Assignee: unassigned at gcc dot gnu.org Reporter: gsocshubham at gmail dot com Target Milestone: --- Host: x86_64-linux-gnu Target: x86_64-linux-gnu Build: x86_64-linux-gnu Created