Re: Code emitted was bloated with no optimisation.

Andrew Haley writes: > On 04/10/2014 04:12 PM, Umesh Kalappa wrote: > >> Please somebody from the group can share their thoughts and will be >> appricate the same. > > But unoptimized code is expected to be large. Why do you expect > otherwise? Sure, but this is a bit extreme. I don't see off-h

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

On Sat, Mar 29, 2014 at 10:51:58AM +0100, Tobias Burnus wrote: > 2014-03-29 Tobias Burnus > > PR other/59055 > * doc/bugreport.texi (Bugs): Remove nodes pointing to the > nirvana. > * doc/gcc.texi (Service): Update description in the @menu > * doc/invoke.texi (Opti

gcc-4.10-20140411 is now available

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

Re: Code emitted was bloated with no optimisation.

Hi Andrew, Appreciate your reply here and yes unoptimized code is expected to be large ,but for the construct like a[i] the below generated code looks crazy to me . ld WA, 10 ld (_a+18), WA ; a[9] = 10; ld WA, (_i) ;code bloated here for a[i] ld

Re: Code emitted was bloated with no optimisation.

Richard , Pmode is defined HImode and private target is 16 bit where int ,short and Pmode is defined HImode and long as SImode. Please do let me know if it requires more information on the target. Thank you ~Umesh On Fri, Apr 11, 2014 at 4:35 PM, Richard Sandiford wrote: > Andrew Haley writ

GCC 4.9.0 Release Candidate available from gcc.gnu.org

GCC 4.9.0 Release Candidate available from gcc.gnu.org The first release candidate for GCC 4.9.0 is available from ftp://gcc.gnu.org/pub/gcc/snapshots/4.9.0-RC-20140411 and shortly its mirrors. It has been generated from SVN revision 209307. I have so far bootstrapped and tested the release

GCC 4.10.0 Status Report (2014-04-11), Stage 1 starts now

Status == The trunk has branched for the GCC 4.9 release and is now open again for general development, stage 1. Please consider not disrupting it too much during the RC phase of GCC 4.9 so it is possible to test important fixes for 4.9.0 on it. As for the version, we are temporarily using 4

GCC 4.9.0 Status Report (2014-04-11)

Status == We have reached zero P1 regressions today (and < 100 important regressions) and the branches/gcc-4_9-branch has been created today and GCC 4.9.0-rc1 built and announced. The branch is now frozen for blocking regressions and documentation fixes only, all changes to the branch require

Re: Unable to match instruction pattern

pshor...@dataworx.com.au writes: > Found it ... > > I had > > (define_expand "zero_extendhisi2" > [ > (set (subreg:HI (match_operand:SI 0 "general_operand" "")0) > (match_operand:HI 1 "general_operand" "")) > (set (subreg:HI (match_dup 0)2) >

Re: Code emitted was bloated with no optimisation.

Umesh Kalappa writes: > Richard , > Pmode is defined HImode and private target is 16 bit where int ,short > and Pmode is defined HImode and long as SImode. > > Please do let me know if it requires more information on the target. In that case I suggest you compile with -da and compare the .expa

Re: [RFC] Detect most integer overflows.

Hi! On Tue, Oct 29, 2013 at 10:41:56AM +0100, Richard Biener wrote: > For a "quick" GCC implementation of the builtins you could expand > them to a open-coded sequence during gimplification. But due to > the issues pointed out above I'm not sure it is the best interface > to support (though now t