This is the mail archive of the
mailing list for the GCC project.
Re: [PATCH, i386]: FIX PR 52698, reload failure with complex address
- From: Uros Bizjak <ubizjak at gmail dot com>
- To: Richard Henderson <rth at redhat dot com>
- Cc: Ulrich Weigand <uweigand at de dot ibm dot com>, gcc-patches at gcc dot gnu dot org, "H.J. Lu" <hjl dot tools at gmail dot com>
- Date: Mon, 23 Apr 2012 10:39:27 +0200
- Subject: Re: [PATCH, i386]: FIX PR 52698, reload failure with complex address
- References: <CAFULd4bfEG1m8hTc=OFRg9UWdKkU-S+hfWxJTZYDqX6XG1d87A@mail.gmail.com> <201203271613.q2RGDg92017837@d06av02.portsmouth.uk.ibm.com> <CAFULd4aEA5jkCMwQftaYDGbFkHJ9BKybN09A6+Otax798S7yDA@mail.gmail.com> <4F71F6CB.email@example.com>
On Tue, Mar 27, 2012 at 7:20 PM, Richard Henderson <firstname.lastname@example.org> wrote:
> On 03/27/12 09:37, Uros Bizjak wrote:
>>> > Now, in this particular case, there might be another option to
>>> > avoid this hassle completely: ?I understand that this UNSPEC is
>>> > simply a magic marker to make the address use the fs: or gs:
>>> > segment override, right? ? Now that GCC supports address spaces,
>>> > it might be possible to model fs:/gs: relative addresses instead
>>> > by using a non-standard address space ...
>> This is an interesting idea, I will look into it.
> Generallized segment overrides via non-standard address spaces
> has been on my to-do list for quite a while...
I have looked a bit to implement this functionality, but address
spaces are somehow coupled with a keyword that describes special
address space. I guess we can't just reuse __thread keyword for this
Ulrich, can you please provide some guidelines on how you think this
proposed functionality should be implemented?