Android native build of GCC

2015-01-08 Thread Andrew Haley
Android native GCC can't support LTO because of a lack of support for dlopen() in the C library. How should we patch the configury to disable LTO by default? Thanks, Andrew.

GCC 5 Status Report (2015-01-08), Stage 4 to start soon

2015-01-08 Thread Jakub Jelinek
The trunk is still in Stage 3 now, which means it is open for general bugfixing, but will enter Stage 4 on Friday, 16th, end of day (timezone of your preference). Once that happens, only wrong-code fixes, regression bugfixes and documentation fixes will be allowed, as is normal for our release bra

IRA : Changes in the cost of putting allocno into memory.

2015-01-08 Thread Ajit Kumar Agarwal
Hello Vladimir: We have made the changes in the ira-color.c in ira_loop_edge_freq and move_spill_restore. The main motivation behind the change is to reduce the memory instruction with respect to the Loops. The changes are done to not to consider the back edge frequency if there are no refere

Re: Support for architectures without hardware interlocks

2015-01-08 Thread Claudiu Zissulescu
Hi David, I've worked on a gcc target that was porting an architecture without hardware interlock support. Basically, you need to emit nop operations to avoid possible hw conflicts. At the moment, this was done by patching the gcc scheduler to do so, Another issue to keep is to check for hardware

Re: Support for architectures without hardware interlocks

2015-01-08 Thread Eric Botcazou
> I've worked on a gcc target that was porting an architecture without > hardware interlock support. Basically, you need to emit nop operations > to avoid possible hw conflicts. At the moment, this was done by > patching the gcc scheduler to do so, Another issue to keep is to check > for hardware c

Re: Support for architectures without hardware interlocks

2015-01-08 Thread Joel Sherrill
On 1/8/2015 9:01 AM, Eric Botcazou wrote: >> I've worked on a gcc target that was porting an architecture without >> hardware interlock support. Basically, you need to emit nop operations >> to avoid possible hw conflicts. At the moment, this was done by >> patching the gcc scheduler to do so, Ano

RE: Support for architectures without hardware interlocks

2015-01-08 Thread Ajit Kumar Agarwal
-Original Message- From: gcc-ow...@gcc.gnu.org [mailto:gcc-ow...@gcc.gnu.org] On Behalf Of Joel Sherrill Sent: Thursday, January 08, 2015 8:59 PM To: Eric Botcazou; Claudiu Zissulescu Cc: gcc@gcc.gnu.org; David Kang Subject: Re: Support for architectures without hardware interlocks On

Re: Support for architectures without hardware interlocks

2015-01-08 Thread Claudiu Zissulescu
Handling the insertion of the nops at the end of RTL pipe needs to take also care of branch shortening optimizations, and filling delay slots. Probably for the given context (only FPU ops) may be a doable approach. //Claudiu On Thu, Jan 8, 2015 at 4:28 PM, Joel Sherrill wrote: > > On 1/8/2015 9:

RE: Support for architectures without hardware interlocks

2015-01-08 Thread Matthew Fortune
> On 1/8/2015 9:01 AM, Eric Botcazou wrote: > >> I've worked on a gcc target that was porting an architecture without > >> hardware interlock support. Basically, you need to emit nop > >> operations to avoid possible hw conflicts. At the moment, this was > >> done by patching the gcc scheduler to d

Re: Support for architectures without hardware interlocks

2015-01-08 Thread Eric Botcazou
> Handling the insertion of the nops at the end of RTL pipe needs to > take also care of branch shortening optimizations, and filling delay > slots. Probably for the given context (only FPU ops) may be a doable > approach. Right, you do it after delay slot filling and before branch shortening. The

contributing to gcc

2015-01-08 Thread Zach Tomkoski
I have been working on changes to extend the functionality of the GCC's built in code coverage tool gcov. What steps would I need to go through to work on getting these additions to be added in to the upstream releases of GCC? Thanks, Zachary Tomkoski

will openacc 2.0 be merged into trunk?

2015-01-08 Thread Mark Farnell
Currently, OpenACC 2.0 is in gomp-4_0-branch, but this email: https://gcc.gnu.org/ml/gcc/2015-01/msg00032.html says that gcc 5.0 will enter stage 4 on Friday 16th January, and from that point onward, only bug fixing patches will be accepted. So will gomp-4_0-branch be able to be merged into the

Re: contributing to gcc

2015-01-08 Thread Jeff Law
On 01/08/15 13:02, Zach Tomkoski wrote: I have been working on changes to extend the functionality of the GCC's built in code coverage tool gcov. What steps would I need to go through to work on getting these additions to be added in to the upstream releases of GCC? https://gcc.gnu.org/contribu

Cross compiling and multiple sysroot question

2015-01-08 Thread Steve Ellcey
(Reposting from gcc-help since I didn't get any replies there.) I have a question about SYSROOT_SUFFIX_SPEC, MULTILIB_OSDIRNAMES, and multilib cross compilers. I was experimenting with a multilib cross compiler and was using SYSROOT_SUFFIX_SPEC to specify different sysroots for different multilib

Re: Cross compiling and multiple sysroot question

2015-01-08 Thread Joseph Myers
On Thu, 8 Jan 2015, Steve Ellcey wrote: > So I set these macros and SPECs: > # m32 and be are defaults > MULTILIB_OPTIONS = m64 mel # In makefile fragment > MULTILIB_DIRNAMES = 64 el # In makefile fragment > MULTILIB_OSDIRNAMES = m64=../lib

gcc-4.8-20150108 is now available

2015-01-08 Thread gccadmin
Snapshot gcc-4.8-20150108 is now available on ftp://gcc.gnu.org/pub/gcc/snapshots/4.8-20150108/ 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