Snapshot gcc-4.3-20070622 is now available on
ftp://gcc.gnu.org/pub/gcc/snapshots/4.3-20070622/
and on various mirrors, see http://gcc.gnu.org/mirrors.html for details.
This snapshot has been generated from the GCC 4.3 SVN branch
with the following options: svn://gcc.gnu.org/svn/gcc/trunk
Roman Zippel wrote:
> Hi,
>
> On Fri, 22 Jun 2007, Kenneth Zadeck wrote:
>
>
>>> Index: gcc/gcc/reg-stack.c
>>> ===
>>> --- gcc.orig/gcc/reg-stack.c
>>> +++ gcc/gcc/reg-stack.c
>>> @@ -2316,6 +2316,12 @@ subst_stack_regs (rtx insn,
> By default all the constant variables will be stored in the far memory
> ('.frodata' section) and will be accessed using "LDE" instruction. The
> non-initialized non-constant variables will be stored in near memory
> ('.nbss' section) and will be accessed using "MOV" instructions. The
> initiali
Hi,
On Fri, 22 Jun 2007, Kenneth Zadeck wrote:
> > Index: gcc/gcc/reg-stack.c
> > ===
> > --- gcc.orig/gcc/reg-stack.c
> > +++ gcc/gcc/reg-stack.c
> > @@ -2316,6 +2316,12 @@ subst_stack_regs (rtx insn, stack regsta
> >if (NOTE_P
Chris Lattner <[EMAIL PROTECTED]> writes:
> On Jun 22, 2007, at 1:41 AM, Sergei Organov wrote:
>
>> Herman Geza <[EMAIL PROTECTED]> writes:
>>
>> [...]
>>
>>> What is the correct way to do this:
>>>
>>> void setNaN(float &v) {
>>> reinterpret_cast(v) = 0x7f81;
>>> }
>>>
>>> without a type-
As noted in http://gcc.gnu.org/bugzilla/show_bug.cgi?id=32437#c5
> I'm not surprised that converting it to an unspec_volatile stops
> us from deleting the instruction, but that wasn't really my concern.
>
> As I said earlier, several other ports use top-level unspecs (rather than
> unspec_volatil
Sergei Organov wrote:
Herman Geza <[EMAIL PROTECTED]> writes:
[...]
What is the correct way to do this:
void setNaN(float &v) {
reinterpret_cast(v) = 0x7f81;
}
without a type-prunning warning? I cannot use the union trick here
Why? Won't the following work?
void setNaN
On Jun 22, 2007, at 1:41 AM, Sergei Organov wrote:
Herman Geza <[EMAIL PROTECTED]> writes:
[...]
What is the correct way to do this:
void setNaN(float &v) {
reinterpret_cast(v) = 0x7f81;
}
without a type-prunning warning? I cannot use the union trick here
Why? Won't the foll
Roman Zippel wrote:
> Hi,
>
> On Wed, 20 Jun 2007, I wrote:
>
>
>> Index: gcc/df-problems.c
>> ===
>> --- gcc/df-problems.c(revision 125811)
>> +++ gcc/df-problems.c(working copy)
>> @@ -1574,7 +1574,7 @@
>>/* Ca
Hello
I am extending the backend of GCC 4.1 with a new operation which maps
directly from a keyword in the language. So far I extended the frontend
and middleend in order to handle this new keyword. I managed to generate
the GIMPLE form and a valid CFG and a RTL object for this keyword.
Basic
Revital1 Eres wrote:
I work with Gcc trees to modify c++ original code and dont find and i
need documentation about trees because the web isnt enought information.
Where are docs about gcc trees and macros to access it?
In GCC wiki you may find useful links:
http://gcc.gnu.org/wiki
(like G
Hi DJ,
>> From the above, I think I like this plan:
Please ignore my earlier post on this topic. We have modified the
proposed solution to incorporate your suggestions. We would be glad if
you could verify it again.
By default all the constant variables will be stored in the far memory
('.frodat
Herman Geza <[EMAIL PROTECTED]> writes:
[...]
> What is the correct way to do this:
>
> void setNaN(float &v) {
> reinterpret_cast(v) = 0x7f81;
> }
>
> without a type-prunning warning? I cannot use the union trick here
Why? Won't the following work?
void setNaN(float &v) {
union {
13 matches
Mail list logo
