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: target/7462: [powerpc] Bad code for unalign access
Date: Tue, 20 May 2003 00:56:00 -0000 [thread overview]
Message-ID: <20030520005601.11921.qmail@sources.redhat.com> (raw)
The following reply was made to PR target/7462; it has been noted by GNATS.
From: Dara Hazeghi <dhazeghi@yahoo.com>
To: Hans-Joachim Widmaier <hjwidmai@foxboro.com>
Cc: gcc-gnats@gcc.gnu.org
Subject: Re: target/7462: [powerpc] Bad code for unalign access
Date: Mon, 19 May 2003 17:54:37 -0700 (PDT)
--- Hans-Joachim Widmaier <hjwidmai@foxboro.com>
wrote:
> Dara Hazeghi:
> >
>
http://gcc.gnu.org/cgi-bin/gnatsweb.pl?cmd=view%20audit-
>
> > trail&database=gcc&pr=7462
> >
> > Hello,
> >
> > gcc 3.1.1 is a bit old, and a fair bit has changed
> since then. Would it
> > be possible for you to check whether this problem
> is still present with
> > gcc 3.3? Thanks,
>
> Hello,
>
> a quick test showed that gcc 3.3 indeed seems to do
> that right. So that
> bug can be closed. Alas, it creates new sections
> which our link script doesn't
> cater for, and a rebuild of the whole project raised
> an internal compiler error.
> Since I'm a bit tight on time, I will defer
> investigating that further and
> revert to gcc 3.2.2.
Sorry to see that 3.3 brings new bugs! When you get a
chance, please report the new problem you've found.
Meanwhile we'll close this bug.
Dara
__________________________________
Do you Yahoo!?
The New Yahoo! Search - Faster. Easier. Bingo.
http://search.yahoo.com
next reply other threads:[~2003-05-20 0:56 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-05-20 0:56 Dara Hazeghi [this message]
-- strict thread matches above, loose matches on Subject: below --
2003-05-21 8:54 ehrhardt
2003-05-17 10:06 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=20030520005601.11921.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).