On Dec 12, 2007, at 12:16 AM, Christopher Lamb wrote:
>>>
>>>
>>> They don't.
>>
>> Ok. It would still be nicer to get to:
> @foo = dllexport global i32 addrspace(1) 0
>>
>> :)
>
> Yes. Bison ate its own head when I tried to do this though. Also
> there are nasty side affects of allowing a
On Dec 11, 2007, at 10:45 PM, Chris Lattner wrote:
@foo = internal global i32 0 addrspace(1)
@foo = weak global i32 0 addrspace(1)
@foo = linkonce global i32 0 addrspace(1)
@foo = appending global i32 0 addrspace(1)
@foo = dllexport global i32 0 addrspace(1)
I prefer that too, but I don't see
>>> @foo = internal global i32 0 addrspace(1)
>>> @foo = weak global i32 0 addrspace(1)
>>> @foo = linkonce global i32 0 addrspace(1)
>>> @foo = appending global i32 0 addrspace(1)
>>> @foo = dllexport global i32 0 addrspace(1)
>>
>> I prefer that too, but I don't see how you're going to get bison
On Dec 11, 2007, at 10:30 PM, Chris Lattner wrote:
How horrible would:
@foo = addrspace(1) external global i32
be?
I like that the order in the decl is the order in the type lots.
These now work with the rules being adjusted.
@foo = extern_weak global i32 addrspace(1)
@foo = external gl
>>> How horrible would:
>>>
@foo = addrspace(1) external global i32
>>>
>>> be?
>>
>> I like that the order in the decl is the order in the type lots.
>>
>> These now work with the rules being adjusted.
>>
>> @foo = extern_weak global i32 addrspace(1)
>> @foo = external global i32 addrspace(1)
On Dec 11, 2007, at 10:12 PM, Christopher Lamb wrote:
On Dec 11, 2007, at 9:16 PM, Chris Lattner wrote:
On Dec 11, 2007, at 9:08 PM, Christopher Lamb wrote:
On Dec 11, 2007, at 8:50 PM, Chris Lattner wrote:
That is a very strong argument to me, but it seems to argue even
more
strongly
On Dec 11, 2007, at 9:16 PM, Chris Lattner wrote:
>
> On Dec 11, 2007, at 9:08 PM, Christopher Lamb wrote:
>
>>
>> On Dec 11, 2007, at 8:50 PM, Chris Lattner wrote:
>>
> That is a very strong argument to me, but it seems to argue even
> more
> strongly for:
>
> @G = constant f
On Dec 11, 2007, at 9:08 PM, Christopher Lamb wrote:
>
> On Dec 11, 2007, at 8:50 PM, Chris Lattner wrote:
>
That is a very strong argument to me, but it seems to argue even
more
strongly for:
@G = constant float addrspace(5) 1.0, section "foo", align 4
Your e
On Dec 11, 2007, at 8:50 PM, Chris Lattner wrote:
That is a very strong argument to me, but it seems to argue even
more
strongly for:
@G = constant float addrspace(5) 1.0, section "foo", align 4
Your example above would then be:
@foo = constant float addrspace(1)* addrspace(2) 1.0
which
>> That is a very strong argument to me, but it seems to argue even more
>> strongly for:
>>
>> @G = constant float addrspace(5) 1.0, section "foo", align 4
>>
>> Your example above would then be:
>>
>>> @foo = constant float addrspace(1)* addrspace(2) 1.0
>>
>> which has type:
>>
>>> float addrspa
On Dec 11, 2007, at 8:34 PM, Chris Lattner wrote:
On Dec 11, 2007, at 5:56 PM, Christopher Lamb wrote:
On Dec 11, 2007, at 3:54 PM, Chris Lattner wrote:
On Dec 11, 2007, at 1:31 AM, Christopher Lamb wrote:
Add information on address space qualifiers for pointer types and
global
declarati
On Dec 11, 2007, at 5:56 PM, Christopher Lamb wrote:
>
> On Dec 11, 2007, at 3:54 PM, Chris Lattner wrote:
>
>> On Dec 11, 2007, at 1:31 AM, Christopher Lamb wrote:
>>> Add information on address space qualifiers for pointer types and
>>> global
>>> declarations to the LangRef.
>>
>> Nice!
>>
>>>
On Dec 11, 2007, at 3:54 PM, Chris Lattner wrote:
On Dec 11, 2007, at 1:31 AM, Christopher Lamb wrote:
Add information on address space qualifiers for pointer types and
global
declarations to the LangRef.
Nice!
[EMAIL PROTECTED] = constant float 1.0 addrspace(5), section "foo", align 4
On Dec 11, 2007, at 1:31 AM, Christopher Lamb wrote:
> Add information on address space qualifiers for pointer types and
> global
> declarations to the LangRef.
Nice!
>
>
> [EMAIL PROTECTED] = constant float 1.0 addrspace(5), section "foo", align 4
Is there a comma after 1.0?
-Chris
_
14 matches
Mail list logo
