gcc-4.8-20130523 is now available

2013-05-23 Thread gccadmin
Snapshot gcc-4.8-20130523 is now available on ftp://gcc.gnu.org/pub/gcc/snapshots/4.8-20130523/ and on various mirrors, see http://gcc.gnu.org/mirrors.html for details. This snapshot has been generated from the GCC 4.8 SVN branch with the following options: svn://gcc.gnu.org/svn/gcc/branches

Re: -Og changes on 4.7.3?

2013-05-23 Thread gds
On 05/13/2013 01:27 AM, Chung-Ju Wu wrote: 2013/5/13 Basile Starynkevitch: This would be for personal use and not necessarily proposed for general release. For personal use it is so much simpler to just build GCC 4.8 and use it. No good reason to stick to a patched GCC 4.7 Cheers. -- I gue

Re: -Og changes on 4.7.3?

2013-05-23 Thread gds
On 05/13/2013 04:19 AM, Richard Biener wrote: On Mon, May 13, 2013 at 3:03 AM, Gene Smith wrote: Could the -Og patches for 4.8 be back-ported to 4.7.3? Or is there important 4.8 dependencies that would make this not practicable? The patches to add -Og shown on gcc.patches list don't look extre

Re: Porting libsanitizer to aarch64

2013-05-23 Thread Richard Henderson
On 05/23/2013 09:43 AM, Richard Earnshaw wrote: > So you're saying the documentation is wrong, or at the very least > misleading... What about dealing with address validation for soft accesses? > Surely we get better code if the SFP ~= HFP since we end up with fewer cases > where we fall back to

Re: Porting libsanitizer to aarch64

2013-05-23 Thread Richard Henderson
On 05/23/2013 09:28 AM, Richard Earnshaw wrote: > Doing that would add significantly to the cost of setting up the frame. It shouldn't... > > FRAME_GROWS_DOWNWARD > Define this macro to nonzero value if the addresses of local variable slots > are > at negative offsets from the frame pointer. Y

Re: Porting libsanitizer to aarch64

2013-05-23 Thread Richard Earnshaw
On 23/05/13 17:36, Jakub Jelinek wrote: On Thu, May 23, 2013 at 05:28:29PM +0100, Richard Earnshaw wrote: FWIW, I would actually recommend against conditionalizing FRAME_GROWS_DOWNWARD for a new port. Just make it _always_ grow down and save yourself the additional code bloat in the backend.

Re: Porting libsanitizer to aarch64

2013-05-23 Thread Jakub Jelinek
On Thu, May 23, 2013 at 05:28:29PM +0100, Richard Earnshaw wrote: > >FWIW, I would actually recommend against conditionalizing > >FRAME_GROWS_DOWNWARD > >for a new port. Just make it _always_ grow down and save yourself the > >additional code bloat in the backend. > > Doing that would add signif

Re: Porting libsanitizer to aarch64

2013-05-23 Thread Richard Earnshaw
On 22/05/13 21:19, Richard Henderson wrote: On 05/22/2013 12:43 AM, Jakub Jelinek wrote: Changing frame grows upward into frame grows downward shouldn't be that hard, see e.g. rs6000 port, where #define FRAME_GROWS_DOWNWARD (flag_stack_protect != 0 || flag_asan != 0) and grep the port where it u