Hi Mikulas,
I see but gas should at least write error and not generate incorrect code.
In which case please could you create a bugzilla entry for this so that we
can track this problem properly.
I did.
Mikulas
Cheers
Nick
___
bug-binutils
Hi
Hi Mikulas,
__asm__ (".global number; number = 0x12345678");
extern void number;
These two declarations are not compatible. The latter declares number as
a data symbol, but the former defines it is an absolute symbol.
I thought that .types do not care for linking,
Andreas is not ta
Hi Mikulas,
I see but gas should at least write error and not generate incorrect code.
In which case please could you create a bugzilla entry for this so that
we can track this problem properly.
Cheers
Nick
___
bug-binutils mailing list
bu
Hi Mikulas,
__asm__ (".global number; number = 0x12345678");
extern void number;
These two declarations are not compatible. The latter declares number as
a data symbol, but the former defines it is an absolute symbol.
I thought that .types do not care for linking,
Andreas is not talking
On Mon, 12 Feb 2007, Andreas Schwab wrote:
Mikulas Patocka <[EMAIL PROTECTED]> writes:
__asm__ (".global number; number = 0x12345678");
extern void number;
These two declarations are not compatible. The latter declares number as
a data symbol, but the former defines it is an absolute symbol
Mikulas Patocka <[EMAIL PROTECTED]> writes:
> __asm__ (".global number; number = 0x12345678");
> extern void number;
These two declarations are not compatible. The latter declares number as
a data symbol, but the former defines it is an absolute symbol. Thus what
you get is undefined behaviour.
Hi
I found the following issue. This program:
#include
__asm__ (".global number; number = 0x12345678");
extern void number;
int main()
{
printf("%p\n", &number);
return 0;
}
works when compiled without -fPIC and segfaults when compiled with -fPIC.
When the program is broken to
