Re: Optimize flag breaks code on many versions of gcc (not all)

2006-06-19 Thread tbp
On 6/19/06, Richard Guenther <[EMAIL PROTECTED]> wrote: Using -mfpmath=sse -msse2 is a workaround if you have a processor that supports SSE2 instructions. As opposed to -ffloat-store, it works reliably and with no performance impact. Such slab test can be turned into a branchless sequence of SS

Re: MIPS RDHWR instruction reordering

2006-06-19 Thread Ian Lance Taylor
Daniel Jacobowitz <[EMAIL PROTECTED]> writes: > On Fri, Jun 16, 2006 at 02:12:29PM -0700, Ian Lance Taylor wrote: > > The computation of the address of x was moved outside the > > conditional--that is, both the rdhwr and the addu moved. You'll have > > to figure out why. gcc shouldn't move instr

Re: MIPS RDHWR instruction reordering

2006-06-19 Thread Daniel Jacobowitz
On Fri, Jun 16, 2006 at 02:12:29PM -0700, Ian Lance Taylor wrote: > The computation of the address of x was moved outside the > conditional--that is, both the rdhwr and the addu moved. You'll have > to figure out why. gcc shouldn't move instructions outside of a > conditional unless they are chea

Re: Output of contrib/compare_tests

2006-06-19 Thread Mike Stump
On Jun 18, 2006, at 2:35 PM, Mike Stein wrote: Is someone else interested in the daily output Or while (1) do, if you have the bandwidth... :-) But, please, just email the results to yourself and try that for a week. :-) This will help shake out the trivial things. You'll also need to ad

Question regarding the "Clean up how cse works" project

2006-06-19 Thread Steven Bosscher
Hi, I have a question about the "Clean up how cse works" project on http://gcc.gnu.org/projects/optimize.html Let me first explain what I am trying to do. I have seen Vlad's patch to make CSE path following remember its state at the end of a path, so that when a new path is followed, a re-scan i

Re: gcc port based on MIPS

2006-06-19 Thread Andrew Pinski
> > "kernel coder" <[EMAIL PROTECTED]> writes: > > > (define_mode_attr divide_condition > > [DF (SF "!TARGET_FIX_SB1 || flag_unsafe_math_optimizations")]) > > ;; (V2SF "TARGET_SB1 && (!TARGET_FIX_SB1 || > > flag_unsafe_math_optimizations)")]) > > > > > > As you can see i just omitted the en

Re: gcc port based on MIPS

2006-06-19 Thread Ian Lance Taylor
"kernel coder" <[EMAIL PROTECTED]> writes: > > V2SF will be created by the line > > VECTOR_MODES (FLOAT, 8); > > Yes you are absolutely right.When i changed the name of file > ABC-modes.def to 1ABC-modes.def ,i got the following error > > make[1]: *** No rule to make target > `../../gcc-4.1.

Re: gcc port based on MIPS

2006-06-19 Thread kernel coder
V2SF will be created by the line VECTOR_MODES (FLOAT, 8); Yes you are absolutely right.When i changed the name of file ABC-modes.def to 1ABC-modes.def ,i got the following error make[1]: *** No rule to make target `../../gcc-4.1.0/gcc/config/ABC/ABC-modes.def', needed by `build/genmodes.o'.

Re: gcc port based on MIPS

2006-06-19 Thread Ian Lance Taylor
"kernel coder" <[EMAIL PROTECTED]> writes: > But when i issued the make all-gcc command .Following error occured > > ../../gcc-4.1.0/gcc/config/ABC/ABC.md: unknown mode `V2SF' > > Would u please explain why this error is being generated.Also a bit of > explaination of 'V2SF' mode will helpful.

Re: addressability checks in the gimplifier

2006-06-19 Thread Olivier Hainque
Hello, As a followup to my previous message enquiring about the intent underlying various addressability checks in the gimplifier, attached is an example of patch which addresses the issues we're observing. It for instance fixes an ICE in in expand_expr_addr_expr_1 on the testcase below: proc

Re: Optimize flag breaks code on many versions of gcc (not all)

2006-06-19 Thread Richard Guenther
On 6/19/06, Seongbae Park <[EMAIL PROTECTED]> wrote: On 6/19/06, Dave Korn <[EMAIL PROTECTED]> wrote: > On 19 June 2006 00:04, Paolo Carlini wrote: > > > Zdenek Dvorak wrote: > > > >> ... I suspect there is something wrong with your > >> code (possibly invoking some undefined

Re: gcc-4.1.0 cross-compile for MIPS

2006-06-19 Thread Kai Ruottu
David Daney kirjoitti: kernel coder wrote: hi, I'm trying to cross compile gcc-4.1.0 for mipsel platform.Following is the sequence of commands which i'm using ../gcc-4.1.0/configure --target=mipsel --without-headres --prefix=/home/shahzad/install/ --with-newlib --enable-languages=c Perhap

Re: Usage of -ftrapv

2006-06-19 Thread Eric Botcazou
> By the way, -ftrapv only works on integral types. When it works. Last time I took a look, it was easily wiped out by optimization. -- Eric Botcazou

Re: Optimize flag breaks code on many versions of gcc (not all)

2006-06-19 Thread Seongbae Park
On 6/19/06, Dave Korn <[EMAIL PROTECTED]> wrote: On 19 June 2006 00:04, Paolo Carlini wrote: > Zdenek Dvorak wrote: > >> ... I suspect there is something wrong with your >> code (possibly invoking some undefined behavior, using uninitialized >> variable, sensitivity to roundi

Re: Usage of -ftrapv

2006-06-19 Thread Ben Elliston
> I'd like to catch automatically over/underflows on floating point > and integer arithmetic. I thought -ftrapv would do the trick but I > don't really understand how it works. By the way, -ftrapv only works on integral types. Ben

gcc port based on MIPS

2006-06-19 Thread kernel coder
hi, I'm trying to port gcc for a processor which is very similar to MIPS.Today i just tried to compile gcc-4.1.0 for this processor by changing configuration files. First i changed the config.sub file in base directory and just added the name of processor ABC. Then i changed the configure.ac file

Re: Coroutines

2006-06-19 Thread Ross Ridge
Ross Ridge wrote: >Hmm? I don't see how the "Lua-style" coroutines you're looking are any >lightweight than what Maurizio Vitale is looking for. They're actually >more heavyweight because you need to implement some method of returning >values to the "coroutine" being yeilded to. Dustin Laurence

RE: Optimize flag breaks code on many versions of gcc (not all)

2006-06-19 Thread Dave Korn
On 19 June 2006 00:04, Paolo Carlini wrote: > Zdenek Dvorak wrote: > >> ... I suspect there is something wrong with your >> code (possibly invoking some undefined behavior, using uninitialized >> variable, sensitivity to rounding errors, or something like that). >> >> > A da