VIS2 pattern review

2011-10-12 Thread Richard Henderson
[ Using the UltraSparc Architecture, Draft D0.9.4, 27 Sep 2010. I believe this is the most recent public manual. It covers VIS1 and VIS2 but not VIS3. ] The comment for fpmerge_vis is not correct. I believe that the operation is representable with (vec_select:V8QI (vec_concat:V8QI

Question about default_elf_asm_named_section function

2011-10-12 Thread Iyer, Balaji V
Hello Everyone, This email is in reference to the "default_elf_asm_named_section" function in the varasm.c file. This function is defined like this: void default_elf_asm_named_section (const char *name, unsigned int flags, tree decl ATTRIBUTE_UNUSED) But

Re: new triplet for x32 psABI?

2011-10-12 Thread Mike Frysinger
On Wed, Oct 12, 2011 at 12:28, H.J. Lu wrote: > 1. The file name of an x32 binary package needs to be marked as x32. i would think this would be completely a package manager issue and out of scope for any ABI project such as x32 -mike

Re: new triplet for x32 psABI?

2011-10-12 Thread H.J. Lu
On Tue, Oct 11, 2011 at 10:03 PM, Michael LIAO wrote: > On Tue, Oct 11, 2011 at 9:21 PM, Mike Frysinger wrote: >> On Tuesday 11 October 2011 22:55:35 Michael LIAO wrote: >>> On Mon, Oct 3, 2011 at 3:34 PM, Mike Frysinger wrote: >>> > On Monday, October 03, 2011 18:25:46 Michael LIAO wrote: >>> >

Re: new triplet for x32 psABI?

2011-10-12 Thread Mike Frysinger
On Wednesday 12 October 2011 01:03:19 Michael LIAO wrote: > I am not asking a dedicated triplet for x32 to be used exclusively for > x32 package build. I am asking additional triplet with enough details > of execution environment (ABI definitely a necessary detail.) for > package which relies on tr

Re: Question on INSN_P and "real" insns

2011-10-12 Thread Georg-Johann Lay
Eric Botcazou schrieb: >> From my understanding a "real" insn is an insn that leads to code that will >> be executed like INSN, CALL_INSN or JUMP_INSN but not DEBUG_INSN that's >> used for location tracking or shipping debug information or CODE_LABEL or >> whatever. >> >> This means that next_real_

Re: Question on INSN_P and "real" insns

2011-10-12 Thread Eric Botcazou
> From my understanding a "real" insn is an insn that leads to code that will > be executed like INSN, CALL_INSN or JUMP_INSN but not DEBUG_INSN that's > used for location tracking or shipping debug information or CODE_LABEL or > whatever. > > This means that next_real_insn depends on -g? And that

Question on INSN_P and "real" insns

2011-10-12 Thread Georg-Johann Lay
In rtl.h there is /* Predicate yielding nonzero iff X is a real insn. */ #define INSN_P(X) \ (NONJUMP_INSN_P (X) || DEBUG_INSN_P (X) || JUMP_P (X) || CALL_P (X)) and in emit-rtl: /* Return the last INSN, CALL_INSN or JUMP_INSN before INSN; or 0, if there is none. This routine does not lo

Re: Combine Pass Behavior

2011-10-12 Thread Eric Botcazou
> The actual problem (or maybe my misunderstanding) is that it > combines the two original insns, then does some substitutions and tries > to match the combined and transformed insn against those defined in the > machine description. If it can't find anything there it reverts > everything and proc

Re: ARM EABI ZCX Ada (4.6.1) almost working

2011-10-12 Thread Eric Botcazou
> Aye, then the Ada side doesn't build. Can you see what it is I'm > missing? You need to further adjust the Ada code (a-exexpr-gcc.adb), which is written for DWARF EH. In particular, you need to rewrite Propagate_Exception to build a proper exception for ARM EH. > I'm beginning to think the w

Re: ARM EABI ZCX Ada (4.6.1) almost working

2011-10-12 Thread Luke A. Guest
On Wed, 2011-10-12 at 09:09 +0200, Eric Botcazou wrote: > > On further thinking about this, I have a feeling this may have something > > to do with the Private1 field of the unwind_exception, but I'm not too > > sure how yet. > > For sure, adding a couple of fields on the Ada side that don't exist

Re: ARM EABI ZCX Ada (4.6.1) almost working

2011-10-12 Thread Eric Botcazou
> On further thinking about this, I have a feeling this may have something > to do with the Private1 field of the unwind_exception, but I'm not too > sure how yet. For sure, adding a couple of fields on the Ada side that don't exist on the C side is highly suspicious. Better get rid of them in a

Re: ARM EABI ZCX Ada (4.6.1) almost working

2011-10-12 Thread Eric Botcazou
> On further thinking about this, I have a feeling this may have something > to do with the Private1 field of the unwind_exception, but I'm not too > sure how yet. For sure, adding a couple of fields on the Ada side that don't exist on the C side is highly suspicious. Better get rid of them in a