Re: [Bug ld/6478] stab warnings cause linker errors

2008-05-14 Thread Nick Clifton
Hi Vincent, (I have not forgotten about this problem, but I am really swamped just at the moment). However, I'm quite surprised when I look at the b-cvs-elf.o symbol table : the _f symbol is both undefined and defined in the .text segment ! This is because of the stab warning - it creates

[Bug ld/6478] stab warnings cause linker errors

2008-05-14 Thread nickc at redhat dot com
--- Additional Comments From nickc at redhat dot com 2008-05-14 09:37 --- Subject: Re: stab warnings cause linker errors Hi Vincent, (I have not forgotten about this problem, but I am really swamped just at the moment). > However, I'm quite surprised when I look at the b-cvs-elf.

[Bug gas/6517] New: cvtsi2sd and cvtsi2ss with mem operand may fail to assemble

2008-05-14 Thread jbeulich at novell dot com
Other than in 2.18, this code .intel_syntax noprefix .text Start: cvtsi2sd xmm0, [ecx] cvtsi2ss xmm0, [ecx] no longer assembles ('ambiguous operand size ...') - the assembler expects a 'dword ptr' operand size specifier, which should only be needed when assembling 64-bit code (whe

[Bug gas/6517] cvtsi2sd and cvtsi2ss with mem operand may fail to assemble

2008-05-14 Thread jbeulich at novell dot com
--- Additional Comments From jbeulich at novell dot com 2008-05-14 12:24 --- This should of course also be adjusted for vcvts12sd/vcvts12ss. -- http://sourceware.org/bugzilla/show_bug.cgi?id=6517 --- You are receiving this mail because: --- You are on the CC list for the bug

[Bug gas/6518] New: wrong diagnostic for vcvtpd2dq/vcvtpd2ps/vcvttpd2dq

2008-05-14 Thread jbeulich at novell dot com
Rather than reporting 'suffix or operands invalid ...' on all three instructions when there is no operand size specifier on the memory operand, 'ambiguous operand size ...' should be reported - the former message implies that a memory operand may not be used at all here: .intel_syntax noprefix .te

[Bug ld/6519] New: __start_SECNAME undocumented

2008-05-14 Thread drow at sources dot redhat dot com
NEWS says (since 2.6): * When an ELF section name is representable as a C identifier (this is not true of most ELF section names), the linker will automatically define symbols __start_SECNAME and __stop_SECNAME, where SECNAME is the section name, at the beginning and the end of the section. This

[Bug ld/6478] stab warnings cause linker errors

2008-05-14 Thread ian at airs dot com
--- Additional Comments From ian at airs dot com 2008-05-14 13:28 --- Subject: Re: stab warnings cause linker errors Nick Clifton <[EMAIL PROTECTED]> writes: > The problem seems to be that when the undefined reference to _f occurs > in b.s before the definition, then when b.o is conver

[Bug ld/6478] stab warnings cause linker errors

2008-05-14 Thread nickc at redhat dot com
--- Additional Comments From nickc at redhat dot com 2008-05-14 15:00 --- Subject: Re: stab warnings cause linker errors Hi Ian, > If I understand what you are getting at, that's how warning symbols > work. Look at MWARN in linker.c. It creates a new symbol, and sets > u.i.link to p