From: Bernd Schmidt <bschmidt@redhat.com>
To: "Bin.Cheng" <amker.cheng@gmail.com>, Richard Henderson <rth@redhat.com>
Cc: gcc-patches List <gcc-patches@gcc.gnu.org>
Subject: Re: [PATCH 9/9] Fix PR 66768
Date: Thu, 08 Oct 2015 09:55:00 -0000 [thread overview]
Message-ID: <56163D75.4080805@redhat.com> (raw)
In-Reply-To: <CAHFci2_eg88Vh26+gAFRa81DDPevfAAemiFjhPVqx2HW+CWPzA@mail.gmail.com>
On 10/08/2015 07:17 AM, Bin.Cheng wrote:
> On Thu, Oct 8, 2015 at 12:59 PM, Richard Henderson <rth@redhat.com> wrote:
>> This is the patch that richi includes in the PR. There will need to
>> be an additional patch to solve an ICE for the AVR backend, as noted
>> in the PR, but this is good enough to solve the bad-code generation
>> problem for the i386 backend.
> Hi Richard,
> For the record, the root cause is in IVO because it fails to preserve
> base object. This patch can only paper over the issue for address
> spaces where PTR type and sizetype have the same length, otherwise IVO
> generates wrong code which can't be walked around by this patch. I
> will take PR66768.
Hmm. In 2012 I submitted a patch "Preserve pointer types in ivopts",
which got lost in review. It was for a different problem than address
spaces, but it might be worth taking a look whether that approach could
help solve this issue.
Bernd
next prev parent reply other threads:[~2015-10-08 9:55 UTC|newest]
Thread overview: 33+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-10-08 5:00 [RFA 0/9] Address space support for x86 Richard Henderson
2015-10-08 5:00 ` [PATCH 4/9] i386: Disallow address spaces with string insns Richard Henderson
2015-10-08 5:00 ` [PATCH 5/9] i386: Add address spaces for fs/gs segments Richard Henderson
2015-10-16 15:29 ` Paolo Bonzini
2015-10-18 23:47 ` Richard Henderson
2015-10-08 5:00 ` [PATCH 9/9] Fix PR 66768 Richard Henderson
2015-10-08 5:17 ` Bin.Cheng
2015-10-08 9:55 ` Bernd Schmidt [this message]
2015-10-08 10:12 ` Bin.Cheng
2015-10-08 10:25 ` Richard Biener
2015-10-08 5:00 ` [PATCH 1/9] Change default of non-overlapping address space conversion Richard Henderson
2015-10-09 10:48 ` Bernd Schmidt
2015-10-08 5:00 ` [PATCH 7/9] i386: Add address space for tls Richard Henderson
2015-10-08 8:30 ` Florian Weimer
2015-10-08 5:00 ` [PATCH 2/9] Relax ADDR_SPACE_GENERIC_P checks for default address space hooks Richard Henderson
2015-10-08 10:10 ` Richard Biener
2015-10-08 5:00 ` [PATCH 3/9] i386: Handle address spaces in movabs patterns Richard Henderson
2015-10-08 5:00 ` [PATCH 8/9] Add TARGET_ADDR_SPACE_ZERO_ADDRESS_VALID Richard Henderson
2015-10-08 10:20 ` Richard Biener
2015-10-09 22:13 ` Richard Henderson
2015-10-12 10:10 ` Richard Biener
2015-10-12 23:27 ` Richard Henderson
2015-10-13 10:13 ` Richard Biener
2015-10-13 15:49 ` Jeff Law
2015-10-13 20:59 ` Richard Henderson
2015-10-14 9:19 ` Richard Biener
2015-10-14 9:22 ` Richard Biener
2015-10-14 21:20 ` Richard Henderson
2015-10-14 15:28 ` Jeff Law
2015-10-14 15:22 ` Jeff Law
2015-10-08 5:00 ` [PATCH 6/9] i386: Replace ix86_address_seg with addr_space_t Richard Henderson
2015-10-08 10:07 ` [RFA 0/9] Address space support for x86 Richard Biener
2015-10-09 22:13 ` 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=56163D75.4080805@redhat.com \
--to=bschmidt@redhat.com \
--cc=amker.cheng@gmail.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).