Re: basic asm and memory clobbers - Proposed solution

2015-12-20 Thread Bernd Edlinger
Hi, On 19.12.2015 19:54, David Wohlferd wrote: > mep: mep_interrupt_saved_reg looks for ASM_INPUT in the body, and saves different registers if found. >>> I'm trying to follow this code. A real challenge since I know nothing >>> about mep. But what I see is: >>> >>> - This routine only

gcc-6-20151220 is now available

2015-12-20 Thread gccadmin
Snapshot gcc-6-20151220 is now available on ftp://gcc.gnu.org/pub/gcc/snapshots/6-20151220/ and on various mirrors, see http://gcc.gnu.org/mirrors.html for details. This snapshot has been generated from the GCC 6 SVN branch with the following options: svn://gcc.gnu.org/svn/gcc/trunk revision

Re: basic asm and memory clobbers - Proposed solution

2015-12-20 Thread David Wohlferd
On 12/20/2015 10:26 AM, Bernd Edlinger wrote: On 19.12.2015 19:54, David Wohlferd wrote: mep: mep_interrupt_saved_reg looks for ASM_INPUT in the body, and saves different registers if found. I'm trying to follow this code. A real challenge since I know nothing about mep. But what I see is: -

Re: basic asm and memory clobbers - Proposed solution

2015-12-20 Thread Segher Boessenkool
On Sun, Dec 20, 2015 at 02:53:15PM -0800, David Wohlferd wrote: > >You do not have to escape the { and } for extended asm, on this target, > >using %{ produces even an error. > > I believe the only the only target that needs to escape {} is i386, > since it's the only one that supports dialects (

Re: basic asm and memory clobbers - Proposed solution

2015-12-20 Thread Bernd Edlinger
On 20.12.2015 23:53, David Wohlferd wrote: > On 12/20/2015 10:26 AM, Bernd Edlinger wrote: >> On 19.12.2015 19:54, David Wohlferd wrote: >> mep: mep_interrupt_saved_reg looks for ASM_INPUT in the body, and >> saves different registers if found. > I'm trying to follow this code. A real

gcc-4.9.1 generating different code between two successive builds

2015-12-20 Thread Cole
Hi, I am busy trying to generate a package for gcc that is consistent between two successive builds, and I am now down to the final few files. I am stuck with the file: cilk-abi-cilk-for.o, which is obviously built with -O2, but between two successive builds, the assembly code generated is differ