Hi Bill,
Alias definitions aren't supported on some platforms. Create a
flag (TARGET_DOES_NOT_SUPPORT_ALIAS_DEFINITIONS) that indicates
this and stops us from creating aliases.
is doing this in the front-end really the right approach? If a
target doesn't
support aliases
On Sep 17, 2007, at 1:59 AM, Duncan Sands wrote:
Hi Bill,
Alias definitions aren't supported on some platforms. Create a
flag (TARGET_DOES_NOT_SUPPORT_ALIAS_DEFINITIONS) that indicates
this and stops us from creating aliases.
is doing this in the front-end really the right approach? If a
Hi Duncan (et al),
I've CC'd Anton since he's the one who knows all about this stuff. Presumably
when A is an alias for B there are two cases: either this is a weak alias or
weakref, meaning that at link time it may turn out that A wasn't an alias for
B after all, or A is a strong alias (a
On 9/17/07, Evan Cheng [EMAIL PROTECTED] wrote:
I don't think Bill's patch affects weakref. Bill?
I don't think so either. But, as pointed out, it will fail for other reasons.
We are already relying on asm printer too much as it is. I'd like not
to add any more target specific knowledge to
On Sep 17, 2007, at 3:35 PM, Bill Wendling wrote:
Hi Duncan (et al),
I've CC'd Anton since he's the one who knows all about this stuff.
Presumably
when A is an alias for B there are two cases: either this is a
weak alias or
weakref, meaning that at link time it may turn out that A
On Sep 17, 2007, at 3:35 PM, Bill Wendling wrote:
Instead, I suggest we output a warning in the f-e that aliases are
not supported,
but still generate the alias in the bitcode. Then we teach the
code generators,
which presumably means the asm printer, to ignore aliases on Darwin
Will
Hi Bill,
Alias definitions aren't supported on some platforms. Create a flag
(TARGET_DOES_NOT_SUPPORT_ALIAS_DEFINITIONS) that indicates this and stops us
from creating aliases.
is doing this in the front-end really the right approach? If a target doesn't
support aliases surely it is LLVM
Hi Duncan,
Alias definitions aren't supported on some platforms. Create a
flag (TARGET_DOES_NOT_SUPPORT_ALIAS_DEFINITIONS) that indicates
this and stops us from creating aliases.
is doing this in the front-end really the right approach? If a
target doesn't
support aliases surely it
Author: void
Date: Wed Sep 12 13:55:13 2007
New Revision: 41882
URL: http://llvm.org/viewvc/llvm-project?rev=41882view=rev
Log:
Alias definitions aren't supported on some platforms. Create a flag
(TARGET_DOES_NOT_SUPPORT_ALIAS_DEFINITIONS) that indicates this and stops us
from creating aliases.
