public inbox for gcc-prs@sourceware.org help / color / mirror / Atom feed
From: Dara Hazeghi <dhazeghi@stanford.edu> To: nobody@gcc.gnu.org Cc: gcc-prs@gcc.gnu.org, Subject: Re: target/7185: [HP-UX] GCC 3.1 crashes with segmentation fault during code compilation Date: Tue, 06 May 2003 18:06:00 -0000 [thread overview] Message-ID: <20030506180602.24928.qmail@sources.redhat.com> (raw) The following reply was made to PR target/7185; it has been noted by GNATS. From: Dara Hazeghi <dhazeghi@stanford.edu> To: gcc-gnats@gcc.gnu.org, gcc-bugs@gcc.gnu.org, nobody@gcc.gnu.org Cc: Subject: Re: target/7185: [HP-UX] GCC 3.1 crashes with segmentation fault during code compilation Date: Tue, 6 May 2003 11:05:17 -0700 http://gcc.gnu.org/cgi-bin/gnatsweb.pl?cmd=view%20audit- trail&database=gcc&pr=7185 Hi all, the testcase in this PR no longer crashes as reported on 3.3 cvs or mainline (20030506). On powerpc-apple-darwin6.5 x hppa2.0w-hp-hpux11.00 cross compiler, source compiles successfully with -O3. I think this PR can be closed. Dara
next reply other threads:[~2003-05-06 18:06 UTC|newest] Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top 2003-05-06 18:06 Dara Hazeghi [this message] -- strict thread matches above, loose matches on Subject: below -- 2003-05-06 18:23 bangerth 2003-05-06 10:56 Giovanni Bajo 2003-05-06 7:26 Dara Hazeghi
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=20030506180602.24928.qmail@sources.redhat.com \ --to=dhazeghi@stanford.edu \ --cc=gcc-prs@gcc.gnu.org \ --cc=nobody@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).