public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "cvs-commit at gcc dot gnu dot org" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug target/14857] [3.4/3.5 Regression]: Gcc segfault on duplicated asm statement Date: Wed, 21 Apr 2004 15:23:00 -0000 [thread overview] Message-ID: <20040421151459.18508.qmail@sources.redhat.com> (raw) In-Reply-To: <20040405193144.14857.hjl@lucon.org> ------- Additional Comments From cvs-commit at gcc dot gnu dot org 2004-04-21 15:14 ------- Subject: Bug 14857 CVSROOT: /cvs/gcc Module name: gcc Branch: gcc-3_4-branch Changes by: hjl@gcc.gnu.org 2004-04-21 15:14:54 Modified files: gcc : ChangeLog gcc/config/ia64: ia64.c Log message: 2004-04-21 H.J. Lu <hongjiu.lu@intel.com> PR target/14857 Backport from mainline: * config/ia64/ia64.c (ia64_encode_section_info): Don't prod global register variables. Patches: http://gcc.gnu.org/cgi-bin/cvsweb.cgi/gcc/gcc/ChangeLog.diff?cvsroot=gcc&only_with_tag=gcc-3_4-branch&r1=2.2326.2.401&r2=2.2326.2.402 http://gcc.gnu.org/cgi-bin/cvsweb.cgi/gcc/gcc/config/ia64/ia64.c.diff?cvsroot=gcc&only_with_tag=gcc-3_4-branch&r1=1.265.2.6&r2=1.265.2.7 -- http://gcc.gnu.org/bugzilla/show_bug.cgi?id=14857
next prev parent reply other threads:[~2004-04-21 15:15 UTC|newest] Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top 2004-04-05 19:32 [Bug target/14857] New: [3.4 " hjl at lucon dot org 2004-04-05 19:41 ` [Bug target/14857] " pinskia at gcc dot gnu dot org 2004-04-06 16:26 ` [Bug target/14857] [3.4/3.5 " hjl at lucon dot org 2004-04-06 17:50 ` hjl at lucon dot org 2004-04-06 17:51 ` hjl at lucon dot org 2004-04-08 2:48 ` wilson at specifixinc dot com 2004-04-08 2:50 ` wilson at specifixinc dot com 2004-04-09 12:52 ` pinskia at gcc dot gnu dot org 2004-04-21 15:23 ` cvs-commit at gcc dot gnu dot org [this message] 2004-04-21 15:54 ` pinskia 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=20040421151459.18508.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).