public inbox for gcc-prs@sourceware.org
help / color / mirror / Atom feed
From: Dara Hazeghi <dhazeghi@yahoo.com>
To: nobody@gcc.gnu.org
Cc: gcc-prs@gcc.gnu.org,
Subject: Re: optimization/9308: [djgpp] gcc 3.2(.1) compilation fail with message: internal error: Segmentation violation
Date: Wed, 14 May 2003 07:56:00 -0000 [thread overview]
Message-ID: <20030514075600.32606.qmail@sources.redhat.com> (raw)
The following reply was made to PR optimization/9308; it has been noted by GNATS.
From: Dara Hazeghi <dhazeghi@yahoo.com>
To: Sergey Erokhin <esl@tlink.kharkov.ua>
Cc: gcc-gnats@gcc.gnu.org
Subject: Re: optimization/9308: [djgpp] gcc 3.2(.1) compilation fail with message: internal error: Segmentation violation
Date: Wed, 14 May 2003 00:48:02 -0700 (PDT)
> DH> Hello,
>
> DH> gcc 3.3 is about to be released, and has a lot
> of changes from 3.2.
> DH> Would it be possible for you to test whether
> this problem still occurs
> DH> with gcc 3.3 prerelease, so we know whether this
> problem is still
> DH> present? Thanks,
>
> sorry, i use only DJGPP
> now latest version of gcc in DJGPP 322b
> i wait 3.3 and test this bug
Fair enough. A final note: this appears to be a host
specific bug, ie it works fine on a cross compiler
(3.2, 3.3 and mainline).
Dara
__________________________________
Do you Yahoo!?
The New Yahoo! Search - Faster. Easier. Bingo.
http://search.yahoo.com
next reply other threads:[~2003-05-14 7:56 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-05-14 7:56 Dara Hazeghi [this message]
-- strict thread matches above, loose matches on Subject: below --
2003-05-14 10:26 giovannibajo
2003-05-13 18:46 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=20030514075600.32606.qmail@sources.redhat.com \
--to=dhazeghi@yahoo.com \
--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: link
Be 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).