[Code Generation] Multi-target

2014-04-06 Thread Claudia Henriques
Hi everybody! My name is Claudia and I am currently working on my master's thesis. I am working with an embedded system, so part of my code will target microblaze, while the remaining code will target x86_64. I would like to know if anybody is able to provide me some work and/or documentation

Re: [Code Generation] Multi-target

2014-04-06 Thread Michael Eager
On 04/06/14 05:29, Claudia Henriques wrote: Hi everybody! My name is Claudia and I am currently working on my master's thesis. I am working with an embedded system, so part of my code will target microblaze, while the remaining code will target x86_64. I would like to know if anybody is able t

Re: HARD_REGNO_CALL_PART_CLOBBERED and regs_invalidated_by_call

2014-04-06 Thread Richard Sandiford
Matthew Fortune writes: > Richard Sandiford writes: >> Matthew Fortune writes: >> > Hi Richard, >> > >> > As part of implementing the new O32 FPXX ABI I am making use of the >> > HARD_REGNO_CALL_PART_CLOBBERED macro to allow odd-numbered >> > floating-point registers to be considered as 'normall

Forcing REG_DEAD?

2014-04-06 Thread Richard Hulme
Hi, Is there a way to force the compiler to consider an operand dead? Specifically, I've got the RL78 backend to generate SET1 and CLR1 instructions to set and clear individual bits. These instructions can either work on the contents of a specific memory address, or indirectly by putting the

Re: Forcing REG_DEAD?

2014-04-06 Thread Richard Sandiford
Richard Hulme writes: > Is there any way of preventing the compiler going with the indirect > alternative? Can a 'parallel' match be defined in the machine > description that indicates the '(set (reg/f:HI...' should be discarded? No, that wouldn't work. The register is only dead if both combi

gcc-4.9-20140406 is now available

2014-04-06 Thread gccadmin
Snapshot gcc-4.9-20140406 is now available on ftp://gcc.gnu.org/pub/gcc/snapshots/4.9-20140406/ and on various mirrors, see http://gcc.gnu.org/mirrors.html for details. This snapshot has been generated from the GCC 4.9 SVN branch with the following options: svn://gcc.gnu.org/svn/gcc/trunk

[gcc/doc] *PING* Re: [patch] Fix texinfo warnings for doc/gcc.texi [was: Re: doc bugs]

2014-04-06 Thread Tobias Burnus
* PING * Tobias Burnus wrote: *PING* Tobias Burnus wrote: H.J. Lu wrote: On Fri, Mar 28, 2014 at 12:41 PM, Mike Stump wrote: Since we are nearing release, I thought I'd mention I see: ../../gcc/gcc/doc/invoke.texi:1114: warning: node next `Overall Options' in menu `C Dialect Options' and i