[Bug target/85401] segfault building code for VAX

2019-10-04 Thread coypu at sdf dot org
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=85401 coypu changed: What|Removed |Added Status|UNCONFIRMED |RESOLVED Resolution|---

[Bug target/85401] segfault building code for VAX

2019-10-01 Thread law at gcc dot gnu.org
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=85401 --- Comment #8 from Jeffrey A. Law --- Author: law Date: Tue Oct 1 19:25:31 2019 New Revision: 276426 URL: https://gcc.gnu.org/viewcvs?rev=276426=gcc=rev Log: PR target/85401 * ira-color.c (allocno_copy_cost_saving): Call

[Bug target/85401] segfault building code for VAX

2019-09-19 Thread coypu at sdf dot org
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=85401 --- Comment #7 from coypu --- I sent a patch to gcc-patches. https://gcc.gnu.org/ml/gcc-patches/2019-09/msg00896.html

[Bug target/85401] segfault building code for VAX

2019-09-11 Thread coypu at sdf dot org
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=85401 --- Comment #6 from coypu --- I imagine I didn't write scheduling for the broken instruction, so it doesn't ever happen. something silly like that, rather than it being a valid fix.

[Bug target/85401] segfault building code for VAX

2019-09-11 Thread coypu at sdf dot org
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=85401 --- Comment #5 from coypu --- Created attachment 46872 --> https://gcc.gnu.org/bugzilla/attachment.cgi?id=46872=edit providing instruction scheduling avoids this crash So, I am trying to beat gcc/vax into shape and incorporate changes from

[Bug target/85401] segfault building code for VAX

2018-04-25 Thread martin at netbsd dot org
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=85401 --- Comment #4 from Martin Husemann --- The costs are missing for various modes: (gdb) p (default_target_ira_int->x_ira_register_move_cost) $6 = {0x0, 0x0, 0x0, 0x0, 0x0, 0x7f7ff7b8c8b0, 0x7f7ff7b8c8b0, 0x0 } (that is: only HImode and SImode

[Bug target/85401] segfault building code for VAX

2018-04-25 Thread martin at netbsd dot org
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=85401 --- Comment #3 from Martin Husemann --- Indeed. Digging a bit with gdb (but in our local 6.4 version) shows: #0 0x009fa7be in allocno_copy_cost_saving (allocno=0x7f7ff679a178, hard_regno=11) at

[Bug target/85401] segfault building code for VAX

2018-04-25 Thread thopre01 at gcc dot gnu.org
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=85401 Thomas Preud'homme changed: What|Removed |Added Status|ASSIGNED|UNCONFIRMED CC|

[Bug target/85401] segfault building code for VAX

2018-04-25 Thread thopre01 at gcc dot gnu.org
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=85401 Thomas Preud'homme changed: What|Removed |Added Status|UNCONFIRMED |ASSIGNED Last reconfirmed|

[Bug target/85401] segfault building code for VAX

2018-04-14 Thread coypu at sdf dot org
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=85401 --- Comment #1 from coypu --- Threw computing resources at the problem, so now I have an "offending" commit. Before this commit, it doesn't segfault. After, it does. commit bbb9b536dd58015b5712a867954d34aae9d9dae5 (HEAD, refs/bisect/bad)