I've been reading your patches...
On Apr 30, 2012, at 4:34 PM, DJ Delorie wrote:
> In going through the Apple test cases, I discovered one HUGE
> disadvantage to using __attribute__ to tag structures for bit reversal
> - it doesn't propogate. I.e.:
This is why pragma exists. :-) Certainly, onc
> Set up a cron job to ping once a day. :-) Did you ever dig up the
> Apple test cases from the APPLE LOCAL work I pointed you at earlier?
> They will be more comprehensive that any testing you've done, and,
> if you get them to all pass, the work should be closer to being
> complete. The featur
On Apr 3, 2012, at 12:57 PM, DJ Delorie wrote:
>> Did you ever dig up the Apple test cases from the APPLE LOCAL work I
>> pointed you at earlier?
>
> Sorry, I read that as "the internal tree at Apple" not "the apple
> branch at fsf". I'll look at it, thanks!
Oh, I just checked the llvm-gcc-4.2 t
> Did you ever dig up the Apple test cases from the APPLE LOCAL work I
> pointed you at earlier?
Sorry, I read that as "the internal tree at Apple" not "the apple
branch at fsf". I'll look at it, thanks!
> They will be more comprehensive that any testing you've done, and,
> if you get them to a
> If it's required for ABI compatibility why is this an attribute and not
> a target hook?
The ABI uses a #pragma; after this is in I'll do a target-specific
pragma handler to set the attribute. Plus, when I originally proposed
the idea, I was told it was generic so make it an attribute ;-)
On Mon, Apr 2, 2012 at 9:41 PM, DJ Delorie wrote:
>
> Ping 6...
>
> It's now been over EIGHT MONTHS since I posted the patch, back in
> stage 1 for 4.7. Can someone please review and/or approve this before
> gcc 4.8's stage 1 is closed? This is needed as a first step for ABI
> compatibility for
On Apr 2, 2012, at 12:41 PM, DJ Delorie wrote:
> Ping 6...
>
> It's now been over EIGHT MONTHS since I posted the patch, back in
> stage 1 for 4.7. Can someone please review and/or approve this before
> gcc 4.8's stage 1 is closed? This is needed as a first step for ABI
> compatibility for rx-el
Ping 6...
It's now been over EIGHT MONTHS since I posted the patch, back in
stage 1 for 4.7. Can someone please review and/or approve this before
gcc 4.8's stage 1 is closed? This is needed as a first step for ABI
compatibility for rx-elf.
> Ping 5...
>
> > Ping 4...
> >
> > > Ping 3? It's
Ping 5...
> Ping 4...
>
> > Ping 3? It's been months with no feedback...
> >
> > > Ping 2 ?
> > >
> > > http://gcc.gnu.org/ml/gcc-patches/2011-07/msg01889.html
> > > http://gcc.gnu.org/ml/gcc-patches/2011-07/msg02555.html
> http://gcc.gnu.org/ml/gcc-patches/2012-01/msg00529.html
http://gcc.gn
Ping 4...
> Ping 3? It's been months with no feedback...
>
> > Ping 2 ?
> >
> > http://gcc.gnu.org/ml/gcc-patches/2011-07/msg01889.html
> > http://gcc.gnu.org/ml/gcc-patches/2011-07/msg02555.html
http://gcc.gnu.org/ml/gcc-patches/2012-01/msg00529.html
Ping 3? It's been months with no feedback...
> Ping 2 ?
>
> http://gcc.gnu.org/ml/gcc-patches/2011-07/msg01889.html
> http://gcc.gnu.org/ml/gcc-patches/2011-07/msg02555.html
Ping 3 ? I'd like to get this in before stage1 ends... There's
RX-specific code that goes with it that can't go in until the core
functionality is approved.
http://gcc.gnu.org/ml/gcc-patches/2011-07/msg01889.html
http://gcc.gnu.org/ml/gcc-patches/2011-07/msg02555.html
http://gcc.gnu.org/ml/gcc-
Ping 2 ?
http://gcc.gnu.org/ml/gcc-patches/2011-07/msg01889.html
http://gcc.gnu.org/ml/gcc-patches/2011-07/msg02555.html
> Seeing little opposition, I plod further... now with documentation
> and a test case. OK yet?
Ping?
http://gcc.gnu.org/ml/gcc-patches/2011-07/msg01889.html
Seeing little opposition, I plod further... now with documentation
and a test case. OK yet?
Index: doc/extend.texi
===
--- doc/extend.texi (revision 176586)
+++ doc/extend.texi (working copy)
@@ -5089,12 +5089,74 @@ Note t
15 matches
Mail list logo