This is the mail archive of the
gcc-patches@gcc.gnu.org
mailing list for the GCC project.
Re: [4.7][SH] Binary compatibility with atomic_test_and_test_trueval != 1
- From: Oleg Endo <oleg dot endo at t-online dot de>
- To: Richard Henderson <rth at redhat dot com>
- Cc: GCC Patches <gcc-patches at gcc dot gnu dot org>, Jakub Jelinek <jakub at redhat dot com>, kkojima at gcc dot gnu dot org
- Date: Fri, 02 Mar 2012 21:39:14 +0100
- Subject: Re: [4.7][SH] Binary compatibility with atomic_test_and_test_trueval != 1
- References: <4F21D3AC.2030500@redhat.com> <1330442171.2929.150.camel@yam-132-YW-E178-FTW> <4F510D55.4090803@redhat.com> <1330720069.2929.227.camel@yam-132-YW-E178-FTW> <4F512ECD.40303@redhat.com>
On Fri, 2012-03-02 at 12:34 -0800, Richard Henderson wrote:
> On 03/02/2012 12:27 PM, Oleg Endo wrote:
> > + This value is used by optabs.c atomic op expansion code as well as in
> > + sync.md. It must be defined as signed char here or else the movqi
> > + pattern will refuse to load it as a QImode constant. */
> > +#undef TARGET_ATOMIC_TEST_AND_SET_TRUEVAL
> > +#define TARGET_ATOMIC_TEST_AND_SET_TRUEVAL ((signed char)0x80)
>
> The fix to use gen_mode_int obviates the need for the (signed char) hack.
>
Ah right, sorry again.
Then I'll rather wait with the whole tas.b patch until the optabs
changes are in.
Cheers,
Oleg