This is the mail archive of the gcc-patches@gcc.gnu.org mailing list for the GCC project.

Index Nav:	[Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav:	[Date Prev] [Date Next]	[Thread Prev] [Thread Next]
Other format:	[Raw text]

Re: [rs6000] Don't emit libcall notes around TLS address

From: Richard Henderson <rth at redhat dot com>
To: Steven Bosscher <stevenb at suse dot de>
Cc: gcc-patches at gcc dot gnu dot org, dje at gcc dot gnu dot org
Date: Wed, 15 Jun 2005 17:51:36 -0700
Subject: Re: [rs6000] Don't emit libcall notes around TLS address
References: <200506111630.49106.stevenb@suse.de> <200506150022.13532.stevenb@suse.de> <20050614233359.GA2755@redhat.com> <200506160132.49575.stevenb@suse.de>

On Thu, Jun 16, 2005 at 01:32:49AM +0200, Steven Bosscher wrote:
> You'd want "*t2 = *t4" but that is not valid GIMPLE.

What the hell are you talking about?  Of course it is.

--
struct large { char x[1000]; };
void foo(struct large *x, struct large *y) { *x = *y; }
--
foo (x, y)
{
<bb 0>:
  *x = *y;
  return;

}
--


r~

Follow-Ups:
- Re: [rs6000] Don't emit libcall notes around TLS address
  - From: Steven Bosscher

References:
- [rs6000] Don't emit libcall notes around TLS address
  - From: Steven Bosscher
- Re: [rs6000] Don't emit libcall notes around TLS address
  - From: Steven Bosscher
- Re: [rs6000] Don't emit libcall notes around TLS address
  - From: Richard Henderson
- Re: [rs6000] Don't emit libcall notes around TLS address
  - From: Steven Bosscher

Index Nav:	[Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav:	[Date Prev] [Date Next]	[Thread Prev] [Thread Next]