> On Mon, Apr 7, 2014 at 8:20 PM, Jan Hubicka wrote:
> >> AFAIK we settled on a simpler one dropping columns at stream-out time
> >> that also helped.
> >>
> >> As for the correct way to do the optimization we agreed(?) that streaming
> >> the locations elsewhere and using references to them is mo
On 15.04.2014 12:54, Jeff Law wrote:
On 04/14/14 18:58, pshor...@dataworx.com.au wrote:
I'm porting to a 16 bit micro and noticed that when optimization is
enabled (function.c:2101), most (non-volatile, non-addressed) stack
variables are copied into virtual registers. I assume this is so the
reg
Hi Community,
We have accepted 5 top-rated student proposals for this year's Google Summer of
Code at GCC. Students, congratulations on your good work thus far, but don't
relax, there is plenty of work ahead!
The accepted proposals are below. The proposals will appear as "Accepted" on
the GS
On 04/14/14 18:58, pshor...@dataworx.com.au wrote:
I'm porting to a 16 bit micro and noticed that when optimization is
enabled (function.c:2101), most (non-volatile, non-addressed) stack
variables are copied into virtual registers. I assume this is so the
register allocator will attempt to alloca
I'm porting to a 16 bit micro and noticed that when optimization is
enabled (function.c:2101), most (non-volatile, non-addressed) stack
variables are copied into virtual registers. I assume this is so the
register allocator will attempt to allocate them to physical registers.
Unfortunately, in
Thanks Richard,
That worked just as you suggested, and ... when I removed my
zero_extendhisi2 the IIRC the target-independent optabs code
generated exactly the same sequence.
Interestingly, I noticed that changing from my define_insn
"zero_extendhisi2" back to the define_expand "zero_extendh
Il 11/04/2014 07:05, Richard Sandiford ha scritto:
Sure, but this is a bit extreme. I don't see off-hand how a[i]
would generate a branch, for starters.
That's an HI+HI->SI addition, with the higher half stored in (SP+2).
The jump is emitted by cstore in order to compute the carry.
On Mon, Apr 14, 2014 at 10:10 AM, Douglas B Rupp wrote:
>
> VxWorks7 has introduced an incompatible unwind.h header file that conflicts
> with gcc's unwind.h (which is a build time header file linked to the
> appropriate source header).
>
> I'd like to propose renaming gcc's unwind.h to unwind-gcc
VxWorks7 has introduced an incompatible unwind.h header file that
conflicts with gcc's unwind.h (which is a build time header file linked
to the appropriate source header).
I'd like to propose renaming gcc's unwind.h to unwind-gcc.h
There are 54 occurrences in the gcc source tree, including
Thank you for your response.
Yves Mocquard.
Le 14/04/2014 11:15, Marc Glisse a écrit :
(wrong list, you want gcc-h...@gcc.gnu.org)
On Mon, 14 Apr 2014, Yves Mocquard wrote:
When I use gcc or g++ , I like when the compilator detects bug, with
a an error of compliation or a warning.
see this
On Mon, Apr 14, 2014 at 2:41 PM, Yves Mocquard wrote:
> Hello !
> I am French, sorry for my bad english.
>
> When I use gcc or g++ , I like when the compilator detects bug, with a an
> error of compliation or a warning.
>
> see this code :
>
> long long fct()
> {
> return 0x123456789;
> }
> in
(wrong list, you want gcc-h...@gcc.gnu.org)
On Mon, 14 Apr 2014, Yves Mocquard wrote:
When I use gcc or g++ , I like when the compilator detects bug, with a an
error of compliation or a warning.
see this code :
long long fct()
{
return 0x123456789;
}
int main()
{
int a = fct();
cerr
Hello !
I am French, sorry for my bad english.
When I use gcc or g++ , I like when the compilator detects bug, with a
an error of compliation or a warning.
see this code :
long long fct()
{
return 0x123456789;
}
int main()
{
int a = fct();
cerr << a << endl;
}
when I compil with
13 matches
Mail list logo
