2010/1/27 fanqifei :
> 2010/1/25 Ulrich Weigand :
>> Qifei Fan wrote:
>>
>>> > But insn#479 is not recognized by recog() in insn-recog.c and the
>>> > compilation failed. (recog only recognizes RTL defined in md, right?)
>>> > Here the backtrace is
>>> > reload--->cleanup_subreg_operands--->extract
On 29 January 2010 11:09, Piotr Wyderski wrote:
> Paolo Carlini wrote:
>
>> Thus, what's the point of submitter fiddling with those Bugzilla
>> fields? Putting some sort of psychological pressure on people actually
>> working on fixing the bugs?
>
> Well, that's true when it comes to high prioritie
Richard Sandiford writes:
>> ** I also consider obsoleting support for the O32 ABI: the SGI linker used
>>is different from the N32/N64 ld, and has repeatedly caused problems
>>which couldn't be resolved even when SGI still had full IRIX
>>support. Also, the ISO C99 support in libc i
Florian Weimer writes:
> Right now, each fresh clone needs to create a compressed pack, which
> takes quite a while.
I ran "git repack -a -d", HTH.
- FChE
My name is Ugo Mezzogori and i am doing my graduation thesis about GCC
architecture.
Can i ask you a few questions?
I know that you rewrote the language Gimple in Tuples instead of trees.
Why did you translare GIMPLE into tuple? which are benefits?
Which is the mechanism?
How do you pass from AST t
Ugo Mezzogori writes:
> I know that you rewrote the language Gimple in Tuples instead of trees.
> Why did you translare GIMPLE into tuple? which are benefits?
GIMPLE uses less memory in the compiler.
> Which is the mechanism?
> How do you pass from AST to GENERIC? and GENERIC to GIMPLE?
> and G
fanqifei writes:
> 2010/1/18 Adam Nemet :
> > Sorry for jumping in late. See make_file_assigment in combine.c.
> >
> > The problem usually is that:
> >
> > (set A (ior (and B C1) OTHER))
> >
> > can only be turned into a bit-insertion if A and B happen to be the same
> > pseudos.
> >
> > Adam
> >
On 01/30/2010 06:48 PM, Ian Lance Taylor wrote:
Uros Bizjak writes:
The target that I would like to support has 8-bit registers, so for
any sane compilation, stack pointer, frame pointer and hard frame
pointer all need to be constructed from at least two registers, to
form 16-bit register
On Sun, Jan 31, 2010 at 6:38 PM, Paolo Carlini wrote:
> it's extremely
> unlikely that the C++ front-end maintainers could even consider
> reviewing patches from a novice for such an hard to implement feature.
That says more about the tangled mess that is gcc then about any
particular programmer'
10 matches
Mail list logo