public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "danglin at gcc dot gnu dot org" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug bootstrap/13713] [3.4/3.5 regression] gnat1 segmentation fault in stage 3 on hppa-linux Date: Sat, 17 Jan 2004 21:33:00 -0000 [thread overview] Message-ID: <20040117213357.12344.qmail@sources.redhat.com> (raw) In-Reply-To: <20040116214440.13713.danglin@gcc.gnu.org> ------- Additional Comments From danglin at gcc dot gnu dot org 2004-01-17 21:33 ------- The regression was introduced by the following patch: 2004-01-15 Geoffrey Keating <geoffk@apple.com> PR pch/13361 * c-typeck.c (constructor_asmspec): Delete. (struct initializer_stack): Delete field 'asmspec'. (start_init): Delete saving of asmspec. (finish_init): Don't update constructor_asmspec. * dwarf2out.c (rtl_for_decl_location): Duplicate string from tree. * stmt.c (expand_asm): Duplicate strings from tree. (expand_asm_operands): Likewise. * tree.c (tree_size): Update computation of size of STRING_CST. (make_node): Don't make STRING_CST nodes. (build_string): Allocate string with tree node. * tree.def (STRING_CST): Update comment. * tree.h (TREE_STRING_POINTER): Adjust for change to STRING_CST. (tree_string): Place contents of string in tree node. * config/sh/sh.c (sh_handle_sp_switch_attribute): Duplicate string from tree. -- What |Removed |Added ---------------------------------------------------------------------------- CC| |geoffk at apple dot com http://gcc.gnu.org/bugzilla/show_bug.cgi?id=13713
next prev parent reply other threads:[~2004-01-17 21:33 UTC|newest] Thread overview: 27+ messages / expand[flat|nested] mbox.gz Atom feed top 2004-01-16 21:44 [Bug ada/13713] New: [3.4 regression] danglin at gcc dot gnu dot org 2004-01-16 21:47 ` [Bug ada/13713] [3.4 regression] gnat1 segmentation fault in stage 3 on hppa-linux danglin at gcc dot gnu dot org 2004-01-16 22:07 ` [Bug bootstrap/13713] " charlet at gcc dot gnu dot org 2004-01-16 22:54 ` [Bug bootstrap/13713] [3.4/3.5 " pinskia at gcc dot gnu dot org 2004-01-17 4:29 ` pinskia at gcc dot gnu dot org 2004-01-17 21:33 ` danglin at gcc dot gnu dot org [this message] 2004-01-17 21:43 ` [Bug ada/13713] " pinskia at gcc dot gnu dot org 2004-01-17 21:46 ` charlet at act-europe dot fr 2004-01-17 21:50 ` pinskia at gcc dot gnu dot org 2004-01-17 21:53 ` charlet at act-europe dot fr 2004-01-18 10:42 ` charlet at gcc dot gnu dot org 2004-01-18 17:22 ` dave at hiauly1 dot hia dot nrc dot ca 2004-01-18 18:07 ` dave at hiauly1 dot hia dot nrc dot ca 2004-01-19 7:01 ` geoffk at apple dot com 2004-01-19 7:02 ` geoffk at gcc dot gnu dot org 2004-01-19 8:30 ` charlet at act-europe dot fr 2004-01-19 8:32 ` charlet at act-europe dot fr 2004-01-19 10:23 ` [Bug middle-end/13713] " charlet at gcc dot gnu dot org 2004-01-19 12:55 ` giovannibajo at libero dot it 2004-01-19 16:13 ` dave at hiauly1 dot hia dot nrc dot ca 2004-01-22 14:11 ` charlet at gcc dot gnu dot org 2004-01-22 15:54 ` dave at hiauly1 dot hia dot nrc dot ca 2004-01-22 15:58 ` [Bug target/13713] " pinskia at gcc dot gnu dot org 2004-01-22 17:38 ` cvs-commit at gcc dot gnu dot org 2004-01-22 17:51 ` cvs-commit at gcc dot gnu dot org 2004-01-22 17:55 ` danglin at gcc dot gnu dot org 2004-01-27 13:04 ` cvs-commit at gcc dot gnu dot org
Reply instructions: You may reply publicly to this message via plain-text email using any one of the following methods: * Save the following mbox file, import it into your mail client, and reply-to-all from there: mbox Avoid top-posting and favor interleaved quoting: https://en.wikipedia.org/wiki/Posting_style#Interleaved_style * Reply using the --to, --cc, and --in-reply-to switches of git-send-email(1): git send-email \ --in-reply-to=20040117213357.12344.qmail@sources.redhat.com \ --to=gcc-bugzilla@gcc.gnu.org \ --cc=gcc-bugs@gcc.gnu.org \ /path/to/YOUR_REPLY https://kernel.org/pub/software/scm/git/docs/git-send-email.html * If your mail client supports setting the In-Reply-To header via mailto: links, try the mailto: linkBe sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions for how to clone and mirror all data and code used for this inbox; as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).