[Bug debug/37022] internal compiler error: in compute_barrier_args_size

2017-01-14 Thread msebor at gcc dot gnu.org
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=37022 Martin Sebor changed: What|Removed |Added Status|NEW |RESOLVED CC|

[Bug debug/37022] internal compiler error: in compute_barrier_args_size

2011-04-28 Thread rguenth at gcc dot gnu.org
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=37022 Richard Guenther changed: What|Removed |Added Target Milestone|4.4.7 |---

[Bug debug/37022] internal compiler error: in compute_barrier_args_size

2011-04-16 Thread jakub at gcc dot gnu.org
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=37022 Jakub Jelinek changed: What|Removed |Added Target Milestone|4.4.6 |4.4.7

[Bug debug/37022] internal compiler error: in compute_barrier_args_size

2010-10-01 Thread jakub at gcc dot gnu.org
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=37022 Jakub Jelinek changed: What|Removed |Added Target Milestone|4.4.5 |4.4.6

[Bug debug/37022] internal compiler error: in compute_barrier_args_size

2010-04-30 Thread jakub at gcc dot gnu dot org
-- jakub at gcc dot gnu dot org changed: What|Removed |Added Target Milestone|4.4.4 |4.4.5 http://gcc.gnu.org/bugzilla/show_bug.cgi?id=37022

[Bug debug/37022] internal compiler error: in compute_barrier_args_size

2010-01-25 Thread jakub at gcc dot gnu dot org
--- Comment #18 from jakub at gcc dot gnu dot org 2010-01-25 08:22 --- It is no longer marged regression, so no longer release critical. Anyway, the goal should be to reenable the asserts in dwarf2out.c and fix the issues, because they really result in wrong unwind info. Only the unwind

[Bug debug/37022] internal compiler error: in compute_barrier_args_size

2010-01-24 Thread ebotcazou at gcc dot gnu dot org
--- Comment #17 from ebotcazou at gcc dot gnu dot org 2010-01-25 06:58 --- Jakub, what to do with this PR? It is still marked "blocker" although it seems to have blocked nothing. -- ebotcazou at gcc dot gnu dot org changed: What|Removed |Added --

[Bug debug/37022] internal compiler error: in compute_barrier_args_size

2010-01-21 Thread jakub at gcc dot gnu dot org
-- jakub at gcc dot gnu dot org changed: What|Removed |Added Target Milestone|4.4.3 |4.4.4 http://gcc.gnu.org/bugzilla/show_bug.cgi?id=37022

[Bug debug/37022] internal compiler error: in compute_barrier_args_size

2009-10-15 Thread jakub at gcc dot gnu dot org
-- jakub at gcc dot gnu dot org changed: What|Removed |Added Target Milestone|4.4.2 |4.4.3 http://gcc.gnu.org/bugzilla/show_bug.cgi?id=37022

[Bug debug/37022] internal compiler error: in compute_barrier_args_size

2009-07-22 Thread jakub at gcc dot gnu dot org
-- jakub at gcc dot gnu dot org changed: What|Removed |Added Target Milestone|4.4.1 |4.4.2 http://gcc.gnu.org/bugzilla/show_bug.cgi?id=37022

[Bug debug/37022] internal compiler error: in compute_barrier_args_size

2009-04-21 Thread jakub at gcc dot gnu dot org
-- jakub at gcc dot gnu dot org changed: What|Removed |Added Target Milestone|4.4.0 |4.4.1 http://gcc.gnu.org/bugzilla/show_bug.cgi?id=37022

[Bug debug/37022] internal compiler error: in compute_barrier_args_size

2009-03-08 Thread amylaar at gcc dot gnu dot org
--- Comment #16 from amylaar at gcc dot gnu dot org 2009-03-08 14:37 --- (In reply to comment #9) > The darwin -m64 failures are then the same problem, cross-jumping of noreturn > calls between different level of stack depths. > I've been wrong about DW_CFA_GNU_args_size being useless f

[Bug debug/37022] internal compiler error: in compute_barrier_args_size

2009-01-13 Thread jakub at gcc dot gnu dot org
--- Comment #15 from jakub at gcc dot gnu dot org 2009-01-13 17:18 --- As the asserts aren't on the trunk, this isn't really a regression, we've been emitting bogus unwind info in these cases (and many more than now) before as well. -- jakub at gcc dot gnu dot org changed: