[Bug target/65416] xtensa: memory allocated by alloca is used before the stack pointer is updated

2015-03-13 Thread jcmvbkbc at gcc dot gnu.org
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=65416 --- Comment #1 from jcmvbkbc at gcc dot gnu.org --- It's ok up to sched2 pass, but sched2 does the following to it: ;; == ;; -- basic block 62 from 252 to 295 -- after reload

[Bug target/65416] New: xtensa: memory allocated by alloca is used before the stack pointer is updated

2015-03-13 Thread jcmvbkbc at gcc dot gnu.org
: normal Priority: P3 Component: target Assignee: unassigned at gcc dot gnu.org Reporter: jcmvbkbc at gcc dot gnu.org Created attachment 35025 -- https://gcc.gnu.org/bugzilla/attachment.cgi?id=35025action=edit preprocessed source with a single function

[Bug target/65730] xtensa: ICE in libstdc++-v3/include/bits/atomic_base.h: In function ‘bool std::atomic_flag_test_and_set_explicit(std::__atomic_flag_base*, std::memory_order)’

2015-05-20 Thread jcmvbkbc at gcc dot gnu.org
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=65730 --- Comment #2 from jcmvbkbc at gcc dot gnu.org --- Author: jcmvbkbc Date: Wed May 20 18:56:14 2015 New Revision: 223452 URL: https://gcc.gnu.org/viewcvs?rev=223452root=gccview=rev Log: Fix PR target/65730 2015-05-20 Max Filippov jcmvb

[Bug target/65730] xtensa: ICE in libstdc++-v3/include/bits/atomic_base.h: In function ‘bool std::atomic_flag_test_and_set_explicit(std::__atomic_flag_base*, std::memory_order)’

2015-05-20 Thread jcmvbkbc at gcc dot gnu.org
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=65730 jcmvbkbc at gcc dot gnu.org changed: What|Removed |Added Status|ASSIGNED|RESOLVED

[Bug target/67586] New: xtensa: ICE with -Os -g -fno-builtin-malloc in dwarf2out_var_location, at dwarf2out.c:22380

2015-09-15 Thread jcmvbkbc at gcc dot gnu.org
Severity: normal Priority: P3 Component: target Assignee: unassigned at gcc dot gnu.org Reporter: jcmvbkbc at gcc dot gnu.org Target Milestone: --- Created attachment 36335 --> https://gcc.gnu.org/bugzilla/attachment.cgi?id=36335=edit test case $

[Bug target/78118] xtensa: ICE in gcc-6.1.0/libgcc/libgcc2.c:1992:1: error: unrecognizable insn

2016-10-26 Thread jcmvbkbc at gcc dot gnu.org
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=78118 --- Comment #2 from jcmvbkbc at gcc dot gnu.org --- The change that made xtensa backend go ICE looks completely unrelated, and indeed, the issue is caused by the side effect of compute_frame_size() function call hidden

[Bug target/78118] xtensa: ICE in gcc-6.1.0/libgcc/libgcc2.c:1992:1: error: unrecognizable insn

2016-10-26 Thread jcmvbkbc at gcc dot gnu.org
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=78118 jcmvbkbc at gcc dot gnu.org changed: What|Removed |Added Status|UNCONFIRMED |ASSIGNED Last

[Bug target/78118] New: xtensa: ICE in gcc-6.1.0/libgcc/libgcc2.c:1992:1: error: unrecognizable insn

2016-10-26 Thread jcmvbkbc at gcc dot gnu.org
: normal Priority: P3 Component: target Assignee: unassigned at gcc dot gnu.org Reporter: jcmvbkbc at gcc dot gnu.org Target Milestone: --- Created attachment 39900 --> https://gcc.gnu.org/bugzilla/attachment.cgi?id=39900=edit preprocessed sou

[Bug target/78118] xtensa: ICE in gcc-6.1.0/libgcc/libgcc2.c:1992:1: error: unrecognizable insn

2016-10-31 Thread jcmvbkbc at gcc dot gnu.org
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=78118 --- Comment #3 from jcmvbkbc at gcc dot gnu.org --- Created attachment 39936 --> https://gcc.gnu.org/bugzilla/attachment.cgi?id=39936=edit tentative patch

[Bug target/78118] xtensa: ICE in gcc-6.1.0/libgcc/libgcc2.c:1992:1: error: unrecognizable insn

2016-11-01 Thread jcmvbkbc at gcc dot gnu.org
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=78118 --- Comment #4 from jcmvbkbc at gcc dot gnu.org --- Author: jcmvbkbc Date: Tue Nov 1 17:16:33 2016 New Revision: 241748 URL: https://gcc.gnu.org/viewcvs?rev=241748=gcc=rev Log: xtensa: Fix PR target/78118 It started failing after the following

[Bug target/78118] xtensa: ICE in gcc-6.1.0/libgcc/libgcc2.c:1992:1: error: unrecognizable insn

2016-11-01 Thread jcmvbkbc at gcc dot gnu.org
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=78118 jcmvbkbc at gcc dot gnu.org changed: What|Removed |Added Status|ASSIGNED|RESOLVED

[Bug target/78603] internal compiler error: in dwarf2out_var_location, at dwarf2out.c:21846

2016-11-29 Thread jcmvbkbc at gcc dot gnu.org
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=78603 --- Comment #3 from jcmvbkbc at gcc dot gnu.org --- Author: jcmvbkbc Date: Tue Nov 29 22:22:13 2016 New Revision: 242979 URL: https://gcc.gnu.org/viewcvs?rev=242979=gcc=rev Log: xtensa: Fix PR target/78603 2016-11-29 Max Filippov <jc

[Bug target/78603] internal compiler error: in dwarf2out_var_location, at dwarf2out.c:21846

2016-11-29 Thread jcmvbkbc at gcc dot gnu.org
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=78603 jcmvbkbc at gcc dot gnu.org changed: What|Removed |Added Status|UNCONFIRMED |RESOLVED

[Bug target/78603] New: internal compiler error: in dwarf2out_var_location, at dwarf2out.c:21846

2016-11-29 Thread jcmvbkbc at gcc dot gnu.org
: normal Priority: P3 Component: target Assignee: unassigned at gcc dot gnu.org Reporter: jcmvbkbc at gcc dot gnu.org Target Milestone: --- Created attachment 40192 --> https://gcc.gnu.org/bugzilla/attachment.cgi?id=40192=edit preprocessed source that trigg

[Bug target/78603] internal compiler error: in dwarf2out_var_location, at dwarf2out.c:21846

2016-11-29 Thread jcmvbkbc at gcc dot gnu.org
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=78603 --- Comment #1 from jcmvbkbc at gcc dot gnu.org --- Created attachment 40193 --> https://gcc.gnu.org/bugzilla/attachment.cgi?id=40193=edit additional patch on top of gcc-5.4.0

[Bug target/78603] internal compiler error: in dwarf2out_var_location, at dwarf2out.c:21846

2016-11-29 Thread jcmvbkbc at gcc dot gnu.org
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=78603 --- Comment #2 from jcmvbkbc at gcc dot gnu.org --- Similar bug: https://gcc.gnu.org/bugzilla/show_bug.cgi?id=48214 And looks like the same problem here: first instruction of zero overhead loop got inserted between the call and its

[Bug target/67586] xtensa: ICE with -Os -g -fno-builtin-malloc in dwarf2out_var_location, at dwarf2out.c:22380

2017-08-09 Thread jcmvbkbc at gcc dot gnu.org
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=67586 jcmvbkbc at gcc dot gnu.org changed: What|Removed |Added Status|WAITING |RESOLVED

[Bug target/78603] internal compiler error: in dwarf2out_var_location, at dwarf2out.c:21846

2017-08-09 Thread jcmvbkbc at gcc dot gnu.org
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=78603 --- Comment #7 from jcmvbkbc at gcc dot gnu.org --- *** Bug 67586 has been marked as a duplicate of this bug. ***

[Bug target/78603] internal compiler error: in dwarf2out_var_location, at dwarf2out.c:21846

2017-05-30 Thread jcmvbkbc at gcc dot gnu.org
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=78603 --- Comment #5 from jcmvbkbc at gcc dot gnu.org --- Author: jcmvbkbc Date: Tue May 30 23:41:58 2017 New Revision: 248708 URL: https://gcc.gnu.org/viewcvs?rev=248708=gcc=rev Log: xtensa: Fix PR target/78603 2017-05-30 Max Filippov <jc

[Bug target/78118] xtensa: ICE in gcc-6.1.0/libgcc/libgcc2.c:1992:1: error: unrecognizable insn

2017-05-30 Thread jcmvbkbc at gcc dot gnu.org
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=78118 --- Comment #6 from jcmvbkbc at gcc dot gnu.org --- Author: jcmvbkbc Date: Wed May 31 00:05:01 2017 New Revision: 248713 URL: https://gcc.gnu.org/viewcvs?rev=248713=gcc=rev Log: xtensa: Fix PR target/78118 It started failing after the following

[Bug target/78603] internal compiler error: in dwarf2out_var_location, at dwarf2out.c:21846

2017-05-30 Thread jcmvbkbc at gcc dot gnu.org
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=78603 --- Comment #6 from jcmvbkbc at gcc dot gnu.org --- Author: jcmvbkbc Date: Wed May 31 00:05:38 2017 New Revision: 248714 URL: https://gcc.gnu.org/viewcvs?rev=248714=gcc=rev Log: xtensa: Fix PR target/78603 2017-05-30 Max Filippov <jc

[Bug target/82181] internal compiler error: in change_address_1, at emit-rtl.c:2126

2017-09-11 Thread jcmvbkbc at gcc dot gnu.org
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=82181 --- Comment #1 from jcmvbkbc at gcc dot gnu.org --- The issue happens in the splitter movdi_internal in the call chain xtensa_split_operand_pair -> adjust_address_1 -> change_address_1, in line gcc_assert (memory_address_addr_space_p (mode

[Bug target/82181] New: internal compiler error: in change_address_1, at emit-rtl.c:2126

2017-09-11 Thread jcmvbkbc at gcc dot gnu.org
Priority: P3 Component: target Assignee: unassigned at gcc dot gnu.org Reporter: jcmvbkbc at gcc dot gnu.org Target Milestone: --- Created attachment 42156 --> https://gcc.gnu.org/bugzilla/attachment.cgi?id=42156=edit preprocessed source that triggers the is

[Bug target/82181] internal compiler error: in change_address_1, at emit-rtl.c:2126

2017-09-11 Thread jcmvbkbc at gcc dot gnu.org
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=82181 --- Comment #3 from jcmvbkbc at gcc dot gnu.org --- Author: jcmvbkbc Date: Mon Sep 11 21:33:36 2017 New Revision: 251986 URL: https://gcc.gnu.org/viewcvs?rev=251986=gcc=rev Log: xtensa: fix PR target/82181 2017-09-11 Max Filippov <jc

[Bug target/82181] internal compiler error: in change_address_1, at emit-rtl.c:2126

2017-09-11 Thread jcmvbkbc at gcc dot gnu.org
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=82181 --- Comment #4 from jcmvbkbc at gcc dot gnu.org --- Author: jcmvbkbc Date: Mon Sep 11 21:44:42 2017 New Revision: 251987 URL: https://gcc.gnu.org/viewcvs?rev=251987=gcc=rev Log: xtensa: fix PR target/82181 2017-09-11 Max Filippov <jc

[Bug target/82181] internal compiler error: in change_address_1, at emit-rtl.c:2126

2017-09-11 Thread jcmvbkbc at gcc dot gnu.org
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=82181 --- Comment #5 from jcmvbkbc at gcc dot gnu.org --- Author: jcmvbkbc Date: Mon Sep 11 21:49:34 2017 New Revision: 251989 URL: https://gcc.gnu.org/viewcvs?rev=251989=gcc=rev Log: xtensa: fix PR target/82181 2017-09-11 Max Filippov <jc

[Bug target/82181] internal compiler error: in change_address_1, at emit-rtl.c:2126

2017-09-11 Thread jcmvbkbc at gcc dot gnu.org
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=82181 --- Comment #6 from jcmvbkbc at gcc dot gnu.org --- Author: jcmvbkbc Date: Mon Sep 11 21:53:38 2017 New Revision: 251990 URL: https://gcc.gnu.org/viewcvs?rev=251990=gcc=rev Log: xtensa: fix PR target/82181 2017-09-11 Max Filippov <jc

[Bug target/82181] internal compiler error: in change_address_1, at emit-rtl.c:2126

2017-09-11 Thread jcmvbkbc at gcc dot gnu.org
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=82181 jcmvbkbc at gcc dot gnu.org changed: What|Removed |Added Status|UNCONFIRMED |RESOLVED

[Bug translation/82185] ICE: Segmentation fault in expand_binop gcc/optabs.c:1137

2017-09-11 Thread jcmvbkbc at gcc dot gnu.org
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=82185 jcmvbkbc at gcc dot gnu.org changed: What|Removed |Added CC||richard.sandiford at linaro

[Bug target/82181] internal compiler error: in change_address_1, at emit-rtl.c:2126

2017-09-11 Thread jcmvbkbc at gcc dot gnu.org
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=82181 --- Comment #2 from jcmvbkbc at gcc dot gnu.org --- With the current gcc mainline compiling the reproducer source results in different ICE: drivers/staging/rtl8188eu/core/rtw_ap.c: In function ‘expire_timeout_chk’: drivers/staging/rtl8188eu/core

[Bug translation/82185] New: ICE: Segmentation fault in expand_binop gcc/optabs.c:1137

2017-09-11 Thread jcmvbkbc at gcc dot gnu.org
Priority: P3 Component: translation Assignee: unassigned at gcc dot gnu.org Reporter: jcmvbkbc at gcc dot gnu.org Target Milestone: --- Created attachment 42157 --> https://gcc.gnu.org/bugzilla/attachment.cgi?id=42157=edit preprocessed source that triggers the is

[Bug target/82185] ICE: Segmentation fault in expand_binop gcc/optabs.c:1137

2017-09-12 Thread jcmvbkbc at gcc dot gnu.org
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=82185 --- Comment #5 from jcmvbkbc at gcc dot gnu.org --- (In reply to Martin Liška from comment #2) > Can't reproduce with x86_64-linux-gnu cross compiler: > > ../configure --enable-languages=c,c++ --disable-multilib > --disable-libsaniti

[Bug target/65416] xtensa: memory allocated by alloca is used before the stack pointer is updated

2018-06-11 Thread jcmvbkbc at gcc dot gnu.org
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=65416 jcmvbkbc at gcc dot gnu.org changed: What|Removed |Added Status|UNCONFIRMED |NEW Last reconfirmed

[Bug target/65416] xtensa: memory allocated by alloca is used before the stack pointer is updated

2018-06-19 Thread jcmvbkbc at gcc dot gnu.org
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=65416 --- Comment #3 from jcmvbkbc at gcc dot gnu.org --- Author: jcmvbkbc Date: Tue Jun 19 18:26:07 2018 New Revision: 261755 URL: https://gcc.gnu.org/viewcvs?rev=261755=gcc=rev Log: xtensa: fix PR target/65416 The issue is caused by reordering

[Bug target/65416] xtensa: memory allocated by alloca is used before the stack pointer is updated

2018-06-19 Thread jcmvbkbc at gcc dot gnu.org
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=65416 jcmvbkbc at gcc dot gnu.org changed: What|Removed |Added Status|NEW |RESOLVED

[Bug target/65416] xtensa: memory allocated by alloca is used before the stack pointer is updated

2018-06-19 Thread jcmvbkbc at gcc dot gnu.org
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=65416 --- Comment #5 from jcmvbkbc at gcc dot gnu.org --- Author: jcmvbkbc Date: Tue Jun 19 20:57:46 2018 New Revision: 261763 URL: https://gcc.gnu.org/viewcvs?rev=261763=gcc=rev Log: xtensa: fix PR target/65416 The issue is caused by reordering

[Bug target/65416] xtensa: memory allocated by alloca is used before the stack pointer is updated

2018-06-19 Thread jcmvbkbc at gcc dot gnu.org
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=65416 --- Comment #6 from jcmvbkbc at gcc dot gnu.org --- Author: jcmvbkbc Date: Tue Jun 19 21:01:22 2018 New Revision: 261764 URL: https://gcc.gnu.org/viewcvs?rev=261764=gcc=rev Log: xtensa: fix PR target/65416 The issue is caused by reordering

[Bug target/65416] xtensa: memory allocated by alloca is used before the stack pointer is updated

2018-06-19 Thread jcmvbkbc at gcc dot gnu.org
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=65416 --- Comment #7 from jcmvbkbc at gcc dot gnu.org --- Author: jcmvbkbc Date: Tue Jun 19 21:08:46 2018 New Revision: 261765 URL: https://gcc.gnu.org/viewcvs?rev=261765=gcc=rev Log: xtensa: fix PR target/65416 The issue is caused by reordering

[Bug target/86814] xtensa port needs updating for CVE-2017-5753

2018-12-31 Thread jcmvbkbc at gcc dot gnu.org
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=86814 --- Comment #1 from jcmvbkbc at gcc dot gnu.org --- Author: jcmvbkbc Date: Mon Dec 31 16:51:36 2018 New Revision: 267488 URL: https://gcc.gnu.org/viewcvs?rev=267488=gcc=rev Log: PR target/86814 Xtensa architecture is not affected by speculation

[Bug target/86772] [meta-bug] tracking port status for CVE-2017-5753

2018-12-31 Thread jcmvbkbc at gcc dot gnu.org
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=86772 Bug 86772 depends on bug 86814, which changed state. Bug 86814 Summary: xtensa port needs updating for CVE-2017-5753 https://gcc.gnu.org/bugzilla/show_bug.cgi?id=86814 What|Removed |Added

[Bug target/86814] xtensa port needs updating for CVE-2017-5753

2018-12-31 Thread jcmvbkbc at gcc dot gnu.org
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=86814 jcmvbkbc at gcc dot gnu.org changed: What|Removed |Added Status|UNCONFIRMED |RESOLVED

[Bug target/90922] Bad prologue generated for call0 ABI functions

2019-06-18 Thread jcmvbkbc at gcc dot gnu.org
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=90922 jcmvbkbc at gcc dot gnu.org changed: What|Removed |Added Status|UNCONFIRMED |RESOLVED

[Bug target/90922] New: Bad prologue generated for call0 ABI functions

2019-06-18 Thread jcmvbkbc at gcc dot gnu.org
: target Assignee: unassigned at gcc dot gnu.org Reporter: jcmvbkbc at gcc dot gnu.org Target Milestone: --- call0 ABI functions that require 129 to 1024 bytes of stack frame and don't save any incoming registers on the stack don't get stack pointer adjustment prologue

[Bug target/90922] Bad prologue generated for call0 ABI functions

2019-06-18 Thread jcmvbkbc at gcc dot gnu.org
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=90922 --- Comment #1 from jcmvbkbc at gcc dot gnu.org --- Author: jcmvbkbc Date: Tue Jun 18 22:19:12 2019 New Revision: 272455 URL: https://gcc.gnu.org/viewcvs?rev=272455=gcc=rev Log: xtensa: fix PR target/90922 Stack pointer adjustment code

[Bug target/91880] ICE: segfault in hwloop_optimize

2019-09-26 Thread jcmvbkbc at gcc dot gnu.org
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=91880 --- Comment #4 from jcmvbkbc at gcc dot gnu.org --- Author: jcmvbkbc Date: Thu Sep 26 20:51:27 2019 New Revision: 276166 URL: https://gcc.gnu.org/viewcvs?rev=276166=gcc=rev Log: xtensa: fix PR target/91880 Xtensa hwloop_optimize segfaults when

[Bug target/91880] ICE: segfault in hwloop_optimize

2019-09-26 Thread jcmvbkbc at gcc dot gnu.org
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=91880 jcmvbkbc at gcc dot gnu.org changed: What|Removed |Added Status|UNCONFIRMED |RESOLVED

[Bug target/90922] Bad prologue generated for call0 ABI functions

2019-09-23 Thread jcmvbkbc at gcc dot gnu.org
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=90922 --- Comment #4 from jcmvbkbc at gcc dot gnu.org --- Author: jcmvbkbc Date: Mon Sep 23 07:48:41 2019 New Revision: 276038 URL: https://gcc.gnu.org/viewcvs?rev=276038=gcc=rev Log: xtensa: backport fix for PR target/90922 Stack pointer adjustment

[Bug target/90922] Bad prologue generated for call0 ABI functions

2019-09-23 Thread jcmvbkbc at gcc dot gnu.org
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=90922 --- Comment #3 from jcmvbkbc at gcc dot gnu.org --- Author: jcmvbkbc Date: Mon Sep 23 07:47:14 2019 New Revision: 276037 URL: https://gcc.gnu.org/viewcvs?rev=276037=gcc=rev Log: xtensa: backport fix for PR target/90922 Stack pointer adjustment

[Bug target/90922] Bad prologue generated for call0 ABI functions

2019-09-23 Thread jcmvbkbc at gcc dot gnu.org
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=90922 --- Comment #5 from jcmvbkbc at gcc dot gnu.org --- Author: jcmvbkbc Date: Mon Sep 23 07:50:40 2019 New Revision: 276039 URL: https://gcc.gnu.org/viewcvs?rev=276039=gcc=rev Log: xtensa: backport fix for PR target/90922 Stack pointer adjustment

[Bug target/91880] New: ICE: segfault in hwloop_optimize

2019-09-24 Thread jcmvbkbc at gcc dot gnu.org
Assignee: unassigned at gcc dot gnu.org Reporter: jcmvbkbc at gcc dot gnu.org Target Milestone: --- Created attachment 46922 --> https://gcc.gnu.org/bugzilla/attachment.cgi?id=46922=edit reproducer source gcc built for xtensa call0 ABI and invoked with the attached sou

[Bug tree-optimization/92938] constprop function is assigned to a different section than the original function

2019-12-13 Thread jcmvbkbc at gcc dot gnu.org
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=92938 jcmvbkbc at gcc dot gnu.org changed: What|Removed |Added Resolution|INVALID |FIXED --- Comment #4 from

[Bug tree-optimization/92938] constprop function is assigned to a different section than the original function

2019-12-13 Thread jcmvbkbc at gcc dot gnu.org
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=92938 jcmvbkbc at gcc dot gnu.org changed: What|Removed |Added Status|RESOLVED|UNCONFIRMED

[Bug tree-optimization/92938] New: constprop function is assigned to a different section than the original function

2019-12-13 Thread jcmvbkbc at gcc dot gnu.org
Severity: normal Priority: P3 Component: tree-optimization Assignee: unassigned at gcc dot gnu.org Reporter: jcmvbkbc at gcc dot gnu.org Target Milestone: --- Created attachment 47496 --> https://gcc.gnu.org/bugzilla/attachment.cgi?id=47496=edit test_bitma

[Bug tree-optimization/92938] constprop function is assigned to a different section than the original function

2019-12-13 Thread jcmvbkbc at gcc dot gnu.org
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=92938 --- Comment #1 from jcmvbkbc at gcc dot gnu.org --- The issue does not reproduce with the current gcc trunk after SVN revision 277054 (generalized IPA predicate on parameter), but it doesn't look like this change fixes the root cause, it just

[Bug target/91880] ICE: segfault in hwloop_optimize

2019-09-24 Thread jcmvbkbc at gcc dot gnu.org
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=91880 --- Comment #1 from jcmvbkbc at gcc dot gnu.org --- Minimal reproducer: void f(unsigned int n, char *a, char *b) { int i; for (i = 0; i <= n - 1; ++i) a[i] = b[i]; } The issue is that entry_bb is em

[Bug target/91880] ICE: segfault in hwloop_optimize

2019-09-25 Thread jcmvbkbc at gcc dot gnu.org
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=91880 --- Comment #3 from jcmvbkbc at gcc dot gnu.org --- (In reply to Martin Liška from comment #2) > Do you have any guess how old is the issue? I guess it's been there since gcc-5 when both call0 ABI support and HW loops optimization w

[Bug tree-optimization/92938] constprop function is assigned to a different section than the original function

2020-01-08 Thread jcmvbkbc at gcc dot gnu.org
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=92938 --- Comment #7 from jcmvbkbc at gcc dot gnu.org --- (In reply to Richard Biener from comment #6) > (In reply to jcmvbkbc from comment #5) > > (In reply to Andrew Pinski from comment #3) > > > I DON'T think it is a GCC issue.

[Bug tree-optimization/92938] constprop function is assigned to a different section than the original function

2020-01-08 Thread jcmvbkbc at gcc dot gnu.org
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=92938 --- Comment #8 from jcmvbkbc at gcc dot gnu.org --- (In reply to jcmvbkbc from comment #7) > or it doesn't take a reference to a variable in .init*. That is, it doesn't have a direct reference to a variable in .init* in its body.

[Bug tree-optimization/92938] constprop function is assigned to a different section than the original function

2020-01-08 Thread jcmvbkbc at gcc dot gnu.org
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=92938 --- Comment #10 from jcmvbkbc at gcc dot gnu.org --- (In reply to Andrew Pinski from comment #9) > (In reply to jcmvbkbc from comment #7) > >It's the reference from .text* to .init* > > which is not present in the source but is g

[Bug target/94584] memw is missing before u8/u16 volatile loads

2020-04-14 Thread jcmvbkbc at gcc dot gnu.org
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=94584 jcmvbkbc at gcc dot gnu.org changed: What|Removed |Added Resolution|--- |FIXED Status

[Bug target/94584] New: memw is missing before u8/u16 volatile loads

2020-04-13 Thread jcmvbkbc at gcc dot gnu.org
: target Assignee: unassigned at gcc dot gnu.org Reporter: jcmvbkbc at gcc dot gnu.org Target Milestone: --- Created attachment 48262 --> https://gcc.gnu.org/bugzilla/attachment.cgi?id=48262=edit minimal reproducer xtensa-elf-gcc -O2 -S volatile.c results in the following c

[Bug target/95571] xtensa stack unwinding doesn't work well with asynchronous register spilling

2020-06-08 Thread jcmvbkbc at gcc dot gnu.org
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=95571 jcmvbkbc at gcc dot gnu.org changed: What|Removed |Added Attachment #48699|0 |1 is obsolete

[Bug target/95571] New: xtensa stack unwinding doesn't work well with asynchronous register spilling

2020-06-08 Thread jcmvbkbc at gcc dot gnu.org
: normal Priority: P3 Component: target Assignee: unassigned at gcc dot gnu.org Reporter: jcmvbkbc at gcc dot gnu.org Target Milestone: --- Xtensa architecture with variable register windows store registers of the spilled register windows in two separate

[Bug target/95571] xtensa stack unwinding doesn't work well with asynchronous register spilling

2020-06-08 Thread jcmvbkbc at gcc dot gnu.org
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=95571 --- Comment #1 from jcmvbkbc at gcc dot gnu.org --- Created attachment 48699 --> https://gcc.gnu.org/bugzilla/attachment.cgi?id=48699=edit minimal reproducer Reproducer spills active register windows in a substitute memcpy as could be d

[Bug target/95571] xtensa stack unwinding doesn't work well with asynchronous register spilling

2020-06-08 Thread jcmvbkbc at gcc dot gnu.org
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=95571 jcmvbkbc at gcc dot gnu.org changed: What|Removed |Added Resolution|--- |FIXED Status

[Bug target/98285] New: xtensa doesn't use addx/subx instructions

2020-12-14 Thread jcmvbkbc at gcc dot gnu.org via Gcc-bugs
Assignee: unassigned at gcc dot gnu.org Reporter: jcmvbkbc at gcc dot gnu.org Target Milestone: --- Prior to version 6.1.0 gcc for xtensa used addx and subx instructions to implement multiplication by small integer constants. After the commit 963ba1b26665 ("comb

[Bug target/98285] xtensa doesn't use addx/subx instructions

2020-12-14 Thread jcmvbkbc at gcc dot gnu.org via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=98285 jcmvbkbc at gcc dot gnu.org changed: What|Removed |Added Resolution|--- |FIXED Status

[Bug target/98470] New: ICE: "error: insn does not satisfy its constraints" with hard FP on xtensa

2020-12-28 Thread jcmvbkbc at gcc dot gnu.org via Gcc-bugs
Severity: normal Priority: P3 Component: target Assignee: unassigned at gcc dot gnu.org Reporter: jcmvbkbc at gcc dot gnu.org Target Milestone: --- Created attachment 49848 --> https://gcc.gnu.org/bugzilla/attachment.cgi?id=49848=edit float-ice.c With

[Bug target/98470] ICE: "error: insn does not satisfy its constraints" with hard FP on xtensa

2020-12-28 Thread jcmvbkbc at gcc dot gnu.org via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=98470 --- Comment #1 from jcmvbkbc at gcc dot gnu.org --- It happens at the reload pass when reload transforms the following RTL that comes to it from the IRA pass: (insn 20 163 164 30 (set (reg:SF 162 [ iftmp.0_87 ]) (mem/u/c:SF (symbol_ref

[Bug target/98470] ICE: "error: insn does not satisfy its constraints" with hard FP on xtensa

2021-01-05 Thread jcmvbkbc at gcc dot gnu.org via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=98470 --- Comment #3 from jcmvbkbc at gcc dot gnu.org --- (In reply to rsand...@gcc.gnu.org from comment #2) > What code should GCC generate if it wants to move the given > MEM into an FP register? The two main options are: > > (1) reload

[Bug target/102336] New: plugins for xtensa-elf gcc cannot be built because xtensa-config.h is missing

2021-09-14 Thread jcmvbkbc at gcc dot gnu.org via Gcc-bugs
Severity: normal Priority: P3 Component: target Assignee: unassigned at gcc dot gnu.org Reporter: jcmvbkbc at gcc dot gnu.org Target Milestone: --- Enabling plugin support in xtensa linux results in the following build error: .../lib/gcc/xtensa-dc232b-elf/10.1.0

[Bug target/102115] symbol address eliminated by the xtensa size optimization

2021-09-07 Thread jcmvbkbc at gcc dot gnu.org via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=102115 jcmvbkbc at gcc dot gnu.org changed: What|Removed |Added Status|ASSIGNED|RESOLVED

[Bug target/102115] symbol address eliminated by the xtensa size optimization

2021-09-06 Thread jcmvbkbc at gcc dot gnu.org via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=102115 jcmvbkbc at gcc dot gnu.org changed: What|Removed |Added CC||jcmvbkbc at gcc dot

[Bug target/105879] DI mode constants are incorrectly loaded into registers on big-endian xtensa

2022-06-08 Thread jcmvbkbc at gcc dot gnu.org via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=105879 jcmvbkbc at gcc dot gnu.org changed: What|Removed |Added Status|ASSIGNED|RESOLVED

[Bug target/105879] DI mode constants are incorrectly loaded into registers on big-endian xtensa

2022-06-07 Thread jcmvbkbc at gcc dot gnu.org via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=105879 jcmvbkbc at gcc dot gnu.org changed: What|Removed |Added Status|UNCONFIRMED |ASSIGNED Ever

[Bug target/105879] New: DI mode constants are incorrectly loaded into registers on big-endian xtensa

2022-06-07 Thread jcmvbkbc at gcc dot gnu.org via Gcc-bugs
: normal Priority: P3 Component: target Assignee: unassigned at gcc dot gnu.org Reporter: jcmvbkbc at gcc dot gnu.org Target Milestone: --- A lot of testsuite tests are failing in big-endian xtensa configuration, e.g. gcc.c-torture/execute/20001031-1.c

[Bug target/107506] [regression] cross-xtensa-esp32s2-elf/gcc-13.0.0_pre20221023: stack smashing detected during RTL pass: expand in function __absvdi2 (gen_movdi)

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

[Bug other/86656] [meta-bug] Issues found with -fsanitize=address

2022-11-28 Thread jcmvbkbc at gcc dot gnu.org via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=86656 Bug 86656 depends on bug 107482, which changed state. Bug 107482 Summary: [10/11/12 Regression] out-of-bounds heap access in IRA since r6-3496-g86f0bef37378a0 https://gcc.gnu.org/bugzilla/show_bug.cgi?id=107482 What|Removed

[Bug rtl-optimization/107482] [10/11/12 Regression] out-of-bounds heap access in IRA since r6-3496-g86f0bef37378a0

2022-11-28 Thread jcmvbkbc at gcc dot gnu.org via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=107482 jcmvbkbc at gcc dot gnu.org changed: What|Removed |Added Resolution|--- |FIXED Status

[Bug target/107645] internal compiler error: RTL check: expected elt 0 type 'e' or 'u', have 'E' (rtx unspec) in symbolic_operand_1, at config/m68k/predicates.md:144

2022-11-16 Thread jcmvbkbc at gcc dot gnu.org via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=107645 jcmvbkbc at gcc dot gnu.org changed: What|Removed |Added Resolution|--- |FIXED Status

[Bug target/107645] internal compiler error: RTL check: expected elt 0 type 'e' or 'u', have 'E' (rtx unspec) in symbolic_operand_1, at config/m68k/predicates.md:144

2022-11-11 Thread jcmvbkbc at gcc dot gnu.org via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=107645 --- Comment #1 from jcmvbkbc at gcc dot gnu.org --- ICE in the reproducer is generated when predicate 'symbolic_operand' is applied to the 'const' node in the following rtl: (insn 342 341 343 35 (set (reg:SI 97) (mem/u:SI (plus:SI

[Bug rtl-optimization/107482] out-of-bounds heap access in IRA

2022-11-03 Thread jcmvbkbc at gcc dot gnu.org via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=107482 --- Comment #5 from jcmvbkbc at gcc dot gnu.org --- I've bisected this issue to commit 86f0bef37378 ("re PR target/61578 (Code size increase for ARM thumb compared to 4.8.x when compiling with -Os)")

[Bug middle-end/107482] out-of-bounds heap access in IRA

2022-10-31 Thread jcmvbkbc at gcc dot gnu.org via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=107482 --- Comment #1 from jcmvbkbc at gcc dot gnu.org --- Created attachment 53807 --> https://gcc.gnu.org/bugzilla/attachment.cgi?id=53807=edit color-check.patch

[Bug rtl-optimization/107482] out-of-bounds heap access in IRA

2022-10-31 Thread jcmvbkbc at gcc dot gnu.org via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=107482 jcmvbkbc at gcc dot gnu.org changed: What|Removed |Added Target|microblazeel-linux-gnu |microblazeel-linux-gnu

[Bug middle-end/107482] New: out-of-bounds heap access in IRA

2022-10-31 Thread jcmvbkbc at gcc dot gnu.org via Gcc-bugs
Assignee: unassigned at gcc dot gnu.org Reporter: jcmvbkbc at gcc dot gnu.org Target Milestone: --- Created attachment 53806 --> https://gcc.gnu.org/bugzilla/attachment.cgi?id=53806=edit _gcov.i Inside the functions update_costs_from_allocno and assign_hard_reg the ma

[Bug target/107549] New: heap-buffer-overflow in xt_true_regnum

2022-11-07 Thread jcmvbkbc at gcc dot gnu.org via Gcc-bugs
Assignee: unassigned at gcc dot gnu.org Reporter: jcmvbkbc at gcc dot gnu.org Target Milestone: --- building gcc.dg/Winfinite-recursion-2.c testcase by the gcc built with ASAN and configured for target=xtensa-linux-uclibc gives the following report: ERROR: AddressSanitizer

[Bug rtl-optimization/107482] out-of-bounds heap access in IRA

2022-10-31 Thread jcmvbkbc at gcc dot gnu.org via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=107482 --- Comment #4 from jcmvbkbc at gcc dot gnu.org --- The original ASAN report from the unmodified code: ==3761891==ERROR: AddressSanitizer: heap-buffer-overflow on address 0x603000450ef8 at pc 0x01a78e5c bp 0x7ffdcf35f2a0 sp 0x7ffdcf35f298

[Bug target/107645] New: internal compiler error: RTL check: expected elt 0 type 'e' or 'u', have 'E' (rtx unspec) in symbolic_operand_1, at config/m68k/predicates.md:144

2022-11-11 Thread jcmvbkbc at gcc dot gnu.org via Gcc-bugs
Product: gcc Version: 13.0 Status: UNCONFIRMED Severity: normal Priority: P3 Component: target Assignee: unassigned at gcc dot gnu.org Reporter: jcmvbkbc at gcc dot gnu.org Target Milestone: --- Created attachment 53884

[Bug target/108919] pure nested function may clobber its static chain pointer in windowed ABI on xtensa

2023-02-25 Thread jcmvbkbc at gcc dot gnu.org via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=108919 jcmvbkbc at gcc dot gnu.org changed: What|Removed |Added Resolution|--- |FIXED Status

[Bug target/98470] ICE: "error: insn does not satisfy its constraints" with hard FP on xtensa

2023-02-26 Thread jcmvbkbc at gcc dot gnu.org via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=98470 --- Comment #4 from jcmvbkbc at gcc dot gnu.org --- I've noticed that this forward-propagation of the literal load followed by not calling the secondary reload function happens when the first literal load instruction has the following in its

[Bug target/108876] return address clobbered in sibcalls resulting in gfortran tests failing on xtensa

2023-02-21 Thread jcmvbkbc at gcc dot gnu.org via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=108876 jcmvbkbc at gcc dot gnu.org changed: What|Removed |Added Resolution|--- |FIXED Status

[Bug target/108876] New: return address clobbered in sibcalls resulting in gfortran tests failing on xtensa

2023-02-21 Thread jcmvbkbc at gcc dot gnu.org via Gcc-bugs
Severity: normal Priority: P3 Component: target Assignee: unassigned at gcc dot gnu.org Reporter: jcmvbkbc at gcc dot gnu.org Target Milestone: --- A number of gfortran tests built with -O3 fail with segfault on call0 xtensa config. E.g. gfortran.dg

[Bug target/108919] New: pure nested function may clobber its static chain pointer in windowed ABI on xtensa

2023-02-24 Thread jcmvbkbc at gcc dot gnu.org via Gcc-bugs
Severity: normal Priority: P3 Component: target Assignee: unassigned at gcc dot gnu.org Reporter: jcmvbkbc at gcc dot gnu.org Target Milestone: --- Created attachment 54525 --> https://gcc.gnu.org/bugzilla/attachment.cgi?id=54525=edit test.c The follow

[Bug target/114158] Wrong FDPIC special-casing in crtstuff produces invalid pointer in init_array

2024-02-28 Thread jcmvbkbc at gcc dot gnu.org via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=114158 --- Comment #4 from jcmvbkbc at gcc dot gnu.org --- > It seems to have been realized that this was not working, as > 6bcbf80c6e2bd8a60d88bbcac3d70ffb67f4888f disabled initfini arrays on > ARM/FDPIC, > but didn't identify the ro

[Bug libgcc/114158] Wrong FDPIC special-casing in crtstuff produces invalid pointer in init_array

2024-02-28 Thread jcmvbkbc at gcc dot gnu.org via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=114158 jcmvbkbc at gcc dot gnu.org changed: What|Removed |Added CC||jcmvbkbc at gcc dot

[Bug libbacktrace/114941] New: libbacktrace build is broken for FDPIC uclibc targets by gcc-14-5173-g2b64e4a54042

2024-05-03 Thread jcmvbkbc at gcc dot gnu.org via Gcc-bugs
Severity: normal Priority: P3 Component: libbacktrace Assignee: unassigned at gcc dot gnu.org Reporter: jcmvbkbc at gcc dot gnu.org CC: ian at gcc dot gnu.org Target Milestone: --- A fix for the https://gcc.gnu.org/bugzilla/show_bug.cgi?id=111315

[Bug libbacktrace/114941] libbacktrace build is broken for FDPIC uclibc targets by r14-5173-g2b64e4a54042

2024-05-04 Thread jcmvbkbc at gcc dot gnu.org via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=114941 --- Comment #3 from jcmvbkbc at gcc dot gnu.org --- (In reply to Ian Lance Taylor from comment #2) > What is the correct way to get the address at which the shared library was > loaded when using FDPIC? There's no single base address i

[Bug libbacktrace/114941] libbacktrace build is broken for FDPIC uclibc targets by r14-5173-g2b64e4a54042

2024-05-27 Thread jcmvbkbc at gcc dot gnu.org via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=114941 --- Comment #4 from jcmvbkbc at gcc dot gnu.org --- Proposed fix: https://gcc.gnu.org/pipermail/gcc-patches/2024-May/652798.html