From: Uros Bizjak <ubizjak@gmail.com>
To: Alexandre Oliva <aoliva@redhat.com>
Cc: Richard Henderson <rth@redhat.com>,
Aldy Hernandez <aldyh@redhat.com>,
gcc-patches@gcc.gnu.org
Subject: Re: [PR55547] fix alias regression on alpha on misaligned symbols (was: Re: do you have time to review this alpha P1 patch?)
Date: Wed, 16 Jan 2013 07:34:00 -0000 [thread overview]
Message-ID: <CAFULd4ZHk06g5frGU=rYdQmZ5EiFx2VU6GbG_jn1Rwfuco_4jQ@mail.gmail.com> (raw)
In-Reply-To: <orlibt6995.fsf_-_@livre.localdomain>
On Wed, Jan 16, 2013 at 5:29 AM, Alexandre Oliva <aoliva@redhat.com> wrote:
>> On 01/15/2013 08:24 AM, Aldy Hernandez wrote:
>>> Ok, it's really an alias.c bug, but it is Alpha, and aoliva has already
>>> provided an unreviewed patch...
>
>>> http://gcc.gnu.org/bugzilla/show_bug.cgi?id=55547
>
>> The patch in #C4 is ok.
>
> Thanks, I'm checking it in (first patch below), but reviewing the logic
> that uses negative sizes, I found a number of places that should use the
> absolute value, and others in which being conservative about negative
> sizes is unnecessary (e.g., when dealing with CONST_INT addresses).
> That was implemented and regstrapped on x86_64-linux-gnu. Uros, would
> you give the second patch a spin on alpha to make sure it doesn't
> regress? Ok to install it?
Thanks, I started a bootstrap/regtest run. If everything goes as
expected, the results will be available in ~10h from now...
Uros.
next prev parent reply other threads:[~2013-01-16 7:34 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <50F582CE.3090201@redhat.com>
[not found] ` <50F585DB.2020706@redhat.com>
2013-01-16 4:30 ` Alexandre Oliva
2013-01-16 7:34 ` Uros Bizjak [this message]
2013-01-16 19:35 ` Uros Bizjak
2013-01-18 11:13 ` [PR55547] fix alias regression on alpha on misaligned symbols Alexandre Oliva
2013-01-16 19:54 ` Richard Henderson
2013-01-17 2:41 ` Alexandre Oliva
2013-01-17 17:05 ` Richard Henderson
2013-01-17 4:16 ` Alexandre Oliva
2013-01-17 17:07 ` Richard Henderson
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='CAFULd4ZHk06g5frGU=rYdQmZ5EiFx2VU6GbG_jn1Rwfuco_4jQ@mail.gmail.com' \
--to=ubizjak@gmail.com \
--cc=aldyh@redhat.com \
--cc=aoliva@redhat.com \
--cc=gcc-patches@gcc.gnu.org \
--cc=rth@redhat.com \
/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).