On 04/18/2014 11:31 PM, Richard Henderson wrote:
> On 04/17/2014 10:14 AM, DJ Delorie wrote:
>> _medium_frame:
>> pushm r6-r12
>> add #-4, r0, r6 ; marked frame-related (fp = sp - 4)
>> mov.L r6, r0
On 04/17/2014 10:14 AM, DJ Delorie wrote:
> _medium_frame:
> pushm r6-r12
> add #-4, r0, r6 ; marked frame-related (fp = sp - 4)
> mov.L r6, r0 ; marked frame-related (sp = fp)
There's your
Colin Prior & Steve Christensen from UNIX Packages/Sunfreeware.
We have been providing GCC as a binary for Solaris for over 20 years.
Initially under sponsorship on www.sunfreeware.com and then more recently
via our subscription site www.unixpackages.com
We aim to make new binary versions availab
Hi, I'm trying to build a race detector for Cilk programs (as an
open-source alternative to the closed-source Intel cilkscreen race
detector).
I'm trying to use the -fsanitize=thread to instrument the loads and
stores, and I'm also use -fcilkplus to generate cilk code at the same
time. My plan i
> Also, is that rule true if we *don't* have a frame pointer? That is,
> when we add a constant to the stack to allocate the frame, should that
> function be marked as frame-related? Or is it just the fp->sp move
> (or potentially an add, if there's outgoing args) that shouldn't be
> marked?
The
