[Bug gas/707] intel syntax vs 'fnstcw ' and 'fldcw'

2005-02-08 Thread jbeulich at novell dot com
--- Additional Comments From jbeulich at novell dot com 2005-02-08 13:47 --- Patch at http://sources.redhat.com/ml/binutils/2005-02/msg00118.html -- What|Removed |Added

[Bug gas/707] intel syntax vs 'fnstcw ' and 'fldcw'

2005-02-09 Thread jbeulich at novell dot com
--- Additional Comments From jbeulich at novell dot com 2005-02-09 08:06 --- patch committed -- What|Removed |Added Status|ASSIGNED|RESOLVED

[Bug gas/847] Error: Zero-length symbol is illegal

2005-04-15 Thread jbeulich at novell dot com
--- Additional Comments From jbeulich at novell dot com 2005-04-15 12:24 --- I see two problems with this suggestion: The small one is that the change to read.c isn't shown. The larger one is that I don't think this is the right thing to do here. tc_canonicalize_symbol_name

[Bug gas/848] gas testsuite FAIL: macros dot

2005-04-15 Thread jbeulich at novell dot com
--- Additional Comments From jbeulich at novell dot com 2005-04-15 13:34 --- This is more wide-spread, other affected targets are hppa, ns32k, and vax. Slightly different reasons cause d30v, dlx, i860, and or32 to fail. For these, the testcase output expectation needs to be adjusted; I

[Bug gas/847] Error: Zero-length symbol is illegal

2005-04-15 Thread jbeulich at novell dot com
--- Additional Comments From jbeulich at novell dot com 2005-04-15 15:26 --- Rejecting zero-length symbols could be undone, but I don't see the point; namely I can't see how you would ever use such a symbol (a standalone # operator is certainly illegal on ia64, and besides tha

[Bug gas/847] Error: Zero-length symbol is illegal

2005-04-18 Thread jbeulich at novell dot com
--- Additional Comments From jbeulich at novell dot com 2005-04-18 08:48 --- I just submitted a patch to undo the rejecting of zero-length symbol names; however, as said before, while this addresses the immediate issue reported here I continue to believe that stuff like .file "

[Bug gas/847] Error: Zero-length symbol is illegal

2005-04-19 Thread jbeulich at novell dot com
--- Additional Comments From jbeulich at novell dot com 2005-04-19 07:01 --- ia64-specific patch applied to mainline; awaiting release manager approval for 2.16... -- http://sources.redhat.com/bugzilla/show_bug.cgi?id=847 --- You are receiving this mail because: --- You are

[Bug gas/847] Error: Zero-length symbol is illegal

2005-04-20 Thread jbeulich at novell dot com
--- Additional Comments From jbeulich at novell dot com 2005-04-20 07:52 --- Also applied to 2.16. -- What|Removed |Added Status|ASSIGNED

[Bug gas/848] gas testsuite FAIL: macros dot

2005-05-06 Thread jbeulich at novell dot com
--- Additional Comments From jbeulich at novell dot com 2005-05-06 06:59 --- Both the sparc failure and the ones mentioned in the previous entry being caused by other reasons should be fixed now. None of the other mentioned targets' maintainers reacted, and since they're not

[Bug binutils/941] gas test macros fails

2005-05-09 Thread jbeulich at novell dot com
--- Additional Comments From jbeulich at novell dot com 2005-05-09 15:42 --- cross reference: bug #848 -- http://sources.redhat.com/bugzilla/show_bug.cgi?id=941 --- You are receiving this mail because: --- You are on the CC list for the bug, or are watching someone who is

[Bug binutils/941] gas test macros fails

2005-05-09 Thread jbeulich at novell dot com
--- Additional Comments From jbeulich at novell dot com 2005-05-09 15:40 --- Yes, a similar issue was reported against sparc; this needs to be fixed in the hppa code. There was some discussion regarding that on the mailing list, and since a few more targets are affected by this I

[Bug gas/1387] New: .equiv may not detect already defined symbol

2005-09-28 Thread jbeulich at novell dot com
: unspecified Status: NEW Severity: normal Priority: P2 Component: gas AssignedTo: unassigned at sources dot redhat dot com ReportedBy: jbeulich at novell dot com CC: bug-binutils at gnu dot org GCC build triplet: *-*-* GCC host

[Bug gas/1387] .equiv may not detect already defined symbol

2005-09-29 Thread jbeulich at novell dot com
--- Additional Comments From jbeulich at novell dot com 2005-09-29 08:29 --- See also http://sourceware.org/ml/binutils/2005-09/msg00280.html and its follow-ups. -- http://sourceware.org/bugzilla/show_bug.cgi?id=1387 --- You are receiving this mail because: --- You are on

[Bug gas/288] expression resolved too early

2005-10-20 Thread jbeulich at novell dot com
--- Additional Comments From jbeulich at novell dot com 2005-10-20 11:31 --- This should be fixed with http://sourceware.org/ml/binutils/2005-10/msg00112.html. -- What|Removed |Added

[Bug gas/1070] Assembler error: too many positional arguments

2006-02-17 Thread jbeulich at novell dot com
--- Additional Comments From jbeulich at novell dot com 2006-02-17 09:58 --- The two patches also break when using macro arguments like m (x)/(y) because parsing stops after the closing parenthesis (another needed difference in behavior from processing of angle brackets

[Bug gas/1387] .equiv may not detect already defined symbol

2006-03-17 Thread jbeulich at novell dot com
--- Additional Comments From jbeulich at novell dot com 2006-03-17 08:26 --- This should be resolved with a checkin from 2005-10-27. -- What|Removed |Added

[Bug gas/3469] GAS encodes corrupt relocation ld reports bad reloc symbol index

2006-11-08 Thread jbeulich at novell dot com
--- Additional Comments From jbeulich at novell dot com 2006-11-08 15:07 --- But this is exactly one of these ambiguous cases: While I agree that it shouldn't silently produce a bad object file, what should gas assume the user wants - the first value seen, or the last one (o

[Bug gas/3469] GAS encodes corrupt relocation ld reports bad reloc symbol index

2006-11-13 Thread jbeulich at novell dot com
--- Additional Comments From jbeulich at novell dot com 2006-11-13 15:09 --- I would think that symbol_equated_reloc_p() for such a symbol should return true, but it doesn't. Investigating further... -- http://sourceware.org/bugzilla/show_bug.cgi?id=3469 --- You are rece

[Bug gas/3469] GAS encodes corrupt relocation ld reports bad reloc symbol index

2006-11-14 Thread jbeulich at novell dot com
--- Additional Comments From jbeulich at novell dot com 2006-11-14 09:38 --- Created an attachment (id=1417) --> (http://sourceware.org/bugzilla/attachment.cgi?id=1417&action=view) tentative patch this one's against 2.17, testing against mainline in progress

[Bug gas/3469] GAS encodes corrupt relocation ld reports bad reloc symbol index

2006-11-15 Thread jbeulich at novell dot com
--- Additional Comments From jbeulich at novell dot com 2006-11-15 11:24 --- patch submitted -- http://sourceware.org/bugzilla/show_bug.cgi?id=3469 --- You are receiving this mail because: --- You are on the CC list for the bug, or are watching someone who is

[Bug gas/3469] GAS encodes corrupt relocation ld reports bad reloc symbol index

2006-11-16 Thread jbeulich at novell dot com
--- Additional Comments From jbeulich at novell dot com 2006-11-16 08:15 --- patch committed -- What|Removed |Added Status|NEW |RESOLVED

[Bug gas/3993] Assembler accepts extra qualifer in Intel syntax

2007-02-07 Thread jbeulich at novell dot com
--- Additional Comments From jbeulich at novell dot com 2007-02-07 15:03 --- The first case must be accepted, since masm allows this as long as the pointer width specified matches the register width. masm fails when the latter isn't true, while gas emit a warning only. I don&#x

[Bug gas/4089] GAS allows using 64-bit regs in 32-bit mode (Intel syntax)

2007-02-28 Thread jbeulich at novell dot com
--- Additional Comments From jbeulich at novell dot com 2007-02-28 08:25 --- As can be seen from the generated opcode, 'rax' is taken as a symbol name rather than a register here. This is the expected behavior when not using % prefixes for register names. --

[Bug gas/14439] New: x86/Intel mode: diagnostics for monitor/mwait operands are issued with wrong operand numbers

2012-08-07 Thread jbeulich at novell dot com
http://sourceware.org/bugzilla/show_bug.cgi?id=14439 Bug #: 14439 Summary: x86/Intel mode: diagnostics for monitor/mwait operands are issued with wrong operand numbers Product: binutils Version: 2.23 (HEAD) Status: NEW

[Bug gas/14439] x86/Intel mode: diagnostics for monitor/mwait operands are issued with wrong operand numbers

2012-08-07 Thread jbeulich at novell dot com
http://sourceware.org/bugzilla/show_bug.cgi?id=14439 --- Comment #1 from Jan Beulich 2012-08-07 10:58:27 UTC --- A patch to carry out the preferred solution can be found at http://www.sourceware.org/ml/binutils/2012-07/msg00173.html. -- Configure bugmail: http://sourceware.org/bugzilla/userpre

[Bug gas/14439] x86/Intel mode: diagnostics for monitor/mwait operands are issued with wrong operand numbers

2012-08-08 Thread jbeulich at novell dot com
http://sourceware.org/bugzilla/show_bug.cgi?id=14439 --- Comment #3 from Jan Beulich 2012-08-08 09:35:37 UTC --- (In reply to comment #2) > Can you add ATTsyntax to existing monitor/wait entries and new > ones with Intelsyntax to i386-opc.tbl deal with it? That might be doable, but as indicated

[Bug gas/17421] Internal error in output_insn during kernel build

2014-10-20 Thread jbeulich at novell dot com
||jbeulich at novell dot com Resolution|FIXED |--- --- Comment #8 from Jan Beulich --- As was pointed out in email (https://sourceware.org/ml/binutils/2014-09/msg00204.html), the fix is wrong and should be reverted/adjusted: VEX-encoded instructions

[Bug gas/20318] New: x86 Intel mode accepts invalid instructions

2016-06-30 Thread jbeulich at novell dot com
Component: gas Assignee: unassigned at sourceware dot org Reporter: jbeulich at novell dot com Target Milestone: --- Created attachment 9373 --> https://sourceware.org/bugzilla/attachment.cgi?id=9373&action=edit small set of examples The attached example demonstrat

[Bug gas/20318] x86 Intel mode accepts invalid instructions

2016-06-30 Thread jbeulich at novell dot com
https://sourceware.org/bugzilla/show_bug.cgi?id=20318 --- Comment #2 from Jan Beulich --- Not sure what you're trying to tell me here: The title clearly says this is an issue in Intel mode only. -- You are receiving this mail because: You are on the CC list for the bug.

[Bug gas/20318] x86 Intel mode accepts invalid instructions

2016-07-01 Thread jbeulich at novell dot com
https://sourceware.org/bugzilla/show_bug.cgi?id=20318 Jan Beulich changed: What|Removed |Added Status|UNCONFIRMED |RESOLVED Resolution|---

[Bug gas/21874] x86: Multiple segment registers in the address are not detected with -masm=intel

2017-11-10 Thread jbeulich at novell dot com
https://sourceware.org/bugzilla/show_bug.cgi?id=21874 Jan Beulich changed: What|Removed |Added CC||jbeulich at novell dot com --- Comment

[Bug gas/21874] x86: Multiple segment registers in the address are not detected with -masm=intel

2017-11-10 Thread jbeulich at novell dot com
https://sourceware.org/bugzilla/show_bug.cgi?id=21874 --- Comment #5 from Jan Beulich --- (I can't, btw, see how to change the status of the bug back from RESOLVED FIXED, or how to re-assign it. Pretty strange a UI limitation as it seems.) -- You are receiving this mail because: You are on the

[Bug gas/21874] x86: Multiple segment registers in the address are not detected with -masm=intel

2017-11-10 Thread jbeulich at novell dot com
https://sourceware.org/bugzilla/show_bug.cgi?id=21874 --- Comment #7 from Jan Beulich --- (In reply to H.J. Lu from comment #6) > If gas doesn't allow multiple segment registers in AT&T syntax, it > shouldn't allow them in Intel syntax. I can only keep telling you that I view maximum possible co

[Bug gas/21874] x86: Multiple segment registers in the address are not detected with -masm=intel

2017-11-10 Thread jbeulich at novell dot com
https://sourceware.org/bugzilla/show_bug.cgi?id=21874 --- Comment #9 from Jan Beulich --- (In reply to H.J. Lu from comment #8) > (In reply to Jan Beulich from comment #7) > > (In reply to H.J. Lu from comment #6) > > > If gas doesn't allow multiple segment registers in AT&T syntax, it > > > shou

[Bug gas/21874] x86: Multiple segment registers in the address are not detected with -masm=intel

2017-11-10 Thread jbeulich at novell dot com
https://sourceware.org/bugzilla/show_bug.cgi?id=21874 --- Comment #11 from Jan Beulich --- (In reply to H.J. Lu from comment #10) > > > In the case of "fs:gs:[eax]", you can replace it with > > > "fs:[eax]" to get the same output. > > > > In straight line code yes. But what if a first override i

[Bug gas/21874] x86: Multiple segment registers in the address are not detected with -masm=intel

2017-11-13 Thread jbeulich at novell dot com
https://sourceware.org/bugzilla/show_bug.cgi?id=21874 --- Comment #15 from Jan Beulich --- (In reply to H.J. Lu from comment #12) > (In reply to Jan Beulich from comment #11) > > (In reply to H.J. Lu from comment #10) > > > Do you have a real example? > > > > No, I don't. But I don't assume you

[Bug gas/21874] x86: Multiple segment registers in the address are not detected with -masm=intel

2017-11-13 Thread jbeulich at novell dot com
https://sourceware.org/bugzilla/show_bug.cgi?id=21874 --- Comment #17 from Jan Beulich --- This is a tentative patch which could replace the bad one. Only tested on 2.29.1 so far. --- 2.29.1/gas/config/tc-i386-intel.c +++ 2.29.1/gas/config/tc-i386-intel.c @@ -411,7 +413,19 @@ static int i386_int

[Bug gas/21874] x86: Multiple segment registers in the address are not detected with -masm=intel

2017-11-13 Thread jbeulich at novell dot com
https://sourceware.org/bugzilla/show_bug.cgi?id=21874 --- Comment #19 from Jan Beulich --- (In reply to H.J. Lu from comment #18) > (In reply to Jan Beulich from comment #17) > > This is a tentative patch which could replace the bad one. Only tested on > > 2.29.1 so far. > > Does GCC behave the

[Bug gas/21874] x86: Multiple segment registers in the address are not detected with -masm=intel

2017-11-14 Thread jbeulich at novell dot com
https://sourceware.org/bugzilla/show_bug.cgi?id=21874 --- Comment #21 from Jan Beulich --- (In reply to H.J. Lu from comment #20) > MASM is totally irrelevant here. This is your opinion, which I don't share. Is this formally written down anywhere? Plus the presence of a MASM syntax expression pa

[Bug gas/21874] x86: Multiple segment registers in the address are not detected with -masm=intel

2017-11-14 Thread jbeulich at novell dot com
https://sourceware.org/bugzilla/show_bug.cgi?id=21874 --- Comment #23 from Jan Beulich --- (In reply to H.J. Lu from comment #22) > The MASM syntax expression parser supports -masm=intel. How that? The compiler doesn't emit expressions, it does all the calculations and emits plain numbers. Are y

[Bug gas/21874] x86: Multiple segment registers in the address are not detected with -masm=intel

2017-11-14 Thread jbeulich at novell dot com
https://sourceware.org/bugzilla/show_bug.cgi?id=21874 --- Comment #25 from Jan Beulich --- (In reply to H.J. Lu from comment #24) > Please don't do that. Why would I not? As indicated, you didn't obtain maintainer approval. In fact I've just checked the mailing list archives - you didn't even th

[Bug gas/22441] New: x86-64: wrong relocation type used for 32-bit index-with-no-base addressing

2017-11-14 Thread jbeulich at novell dot com
Severity: normal Priority: P2 Component: gas Assignee: unassigned at sourceware dot org Reporter: jbeulich at novell dot com Target Milestone: --- This piece of code .text .intel_syntax noprefix .global _start _start: ret

[Bug gas/21874] x86: Multiple segment registers in the address are not detected with -masm=intel

2017-11-30 Thread jbeulich at novell dot com
https://sourceware.org/bugzilla/show_bug.cgi?id=21874 --- Comment #26 from Jan Beulich --- https://xenbits.xen.org/gitweb/?p=xen.git;a=commitdiff;h=eb0660c6950e08e44fdfeca3e29320382e2a1554 replaces the original commit. -- You are receiving this mail because: You are on the CC list for the bug.

[Bug gas/22441] x86-64: wrong relocation type used for 32-bit index-with-no-base addressing

2017-11-30 Thread jbeulich at novell dot com
https://sourceware.org/bugzilla/show_bug.cgi?id=22441 Jan Beulich changed: What|Removed |Added Status|UNCONFIRMED |RESOLVED Resolution|---

[Bug gas/22871] Encode instructions of 64-bit registers without the REX_W bit

2018-02-21 Thread jbeulich at novell dot com
https://sourceware.org/bugzilla/show_bug.cgi?id=22871 Jan Beulich changed: What|Removed |Added CC||jbeulich at novell dot com --- Comment

[Bug gas/22871] Encode instructions of 64-bit operand without the REX_W bit

2018-02-22 Thread jbeulich at novell dot com
https://sourceware.org/bugzilla/show_bug.cgi?id=22871 --- Comment #6 from Jan Beulich --- (In reply to H.J. Lu from comment #5) > I updated users/hjl/optimize branch to encode > > testq $imm31, mem > > as > > testl $imm31, mem > > only at -O2. I was about to suggest that, also becaus

[Bug gas/22871] Encode instructions of 64-bit operand without the REX_W bit

2018-02-22 Thread jbeulich at novell dot com
https://sourceware.org/bugzilla/show_bug.cgi?id=22871 --- Comment #13 from Jan Beulich --- One more pair of cases to consider is conversion of word/dword/qword add/sub with an immediate of 128 to sub/add with -128 as immediate. -- You are receiving this mail because: You are on the CC list for

[Bug gas/24434] Missing testsuite coverage for AVX512F gathers (and scatters?) with no base register

2019-04-10 Thread jbeulich at novell dot com
https://sourceware.org/bugzilla/show_bug.cgi?id=24434 --- Comment #2 from Jan Beulich --- (In reply to Martin Liška from comment #1) > Fixed in bintuils with: > > commit 629cfaf1b0fbb32a985607c774bd8e7870b9fa94 (HEAD, refs/bisect/bad) > Author: Jan Beulich > Date: Mon Jul 30 17:25:05 2018 +02

[Bug gas/24546] x86-64 far jump/call encoding issues

2019-05-16 Thread jbeulich at novell dot com
https://sourceware.org/bugzilla/show_bug.cgi?id=24546 Jan Beulich changed: What|Removed |Added CC||jbeulich at novell dot com --- Comment

[Bug gas/24546] x86-64 far jump/call encoding issues

2019-05-16 Thread jbeulich at novell dot com
https://sourceware.org/bugzilla/show_bug.cgi?id=24546 --- Comment #8 from Jan Beulich --- (In reply to H.J. Lu from comment #7) > Care to make a patch? Well, I've added it to my list of things to look into, but there are various other things higher up that list, so it's not clear at all when I'd

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

2008-05-14 Thread jbeulich at novell dot com
Priority: P2 Component: gas AssignedTo: unassigned at sources dot redhat dot com ReportedBy: jbeulich at novell dot com CC: bug-binutils at gnu dot org GCC build triplet: i686-pc-linux GCC host triplet: i686-pc-linux GCC target triplet: i686-pc-linux h

[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 gas/6518] New: wrong diagnostic for vcvtpd2dq/vcvtpd2ps/vcvttpd2dq

2008-05-14 Thread jbeulich at novell dot com
Severity: normal Priority: P2 Component: gas AssignedTo: unassigned at sources dot redhat dot com ReportedBy: jbeulich at novell dot com CC: bug-binutils at gnu dot org GCC build triplet: i686-pc-linux GCC host triplet: i686-pc-linux GCC target tr

[Bug gas/6518] wrong diagnostic for movsx/movzx/vcvtpd2dq/vcvtpd2ps/vcvttpd2dq

2008-05-26 Thread jbeulich at novell dot com
--- Additional Comments From jbeulich at novell dot com 2008-05-26 08:47 --- I disagree to this approach of fixing the issue - for one, the existing diagnostic shouldn't become more vague for cases it was precise for so far, and secondly in other cases operand size ambiguity is

[Bug gas/11731] -msyntax=intel nasm-incompatible compilation

2010-06-20 Thread jbeulich at novell dot com
--- Additional Comments From jbeulich at novell dot com 2010-06-21 06:51 --- Actually, masm considers this a syntax error (i.e. doesn't allow dword et al not any place a number would be accepted. Kind of confusing, but in any case not a hint to accept this (unconditionally) the way

[Bug gas/11732] internal error on invalid code && -msyntax=intel

2010-06-21 Thread jbeulich at novell dot com
--- Additional Comments From jbeulich at novell dot com 2010-06-21 10:36 --- For what it's worth, the same doesn't abort in 2.20.1. -- http://sourceware.org/bugzilla/show_bug.cgi?id=11732 --- You are receiving this mail because: --- You are on the CC list for t

[Bug gas/11731] -msyntax=intel nasm-incompatible compilation

2010-06-21 Thread jbeulich at novell dot com
--- Additional Comments From jbeulich at novell dot com 2010-06-21 15:32 --- (In reply to comment #5) > When does MASM treat BYTE, WORD, DWORD, ... as numbers? As operands to most operators (or as an expression on their own), but apparently not (generally) to []. Beyond that, as w

[Bug gas/11806] FAIL: i386 intelbad with -O0

2010-07-12 Thread jbeulich at novell dot com
--- Additional Comments From jbeulich at novell dot com 2010-07-12 10:54 --- The error message you quote is certainly right for that line. Also, I cannot reproduce the behavior here. Could you attach the full gas/testsuite/gas.log, or at least the full fragment pertaining to that

[Bug gas/11806] FAIL: i386 intelbad with -O0

2010-07-12 Thread jbeulich at novell dot com
--- Additional Comments From jbeulich at novell dot com 2010-07-12 15:17 --- (In reply to comment #2) > When binutils is compiled with -O0, this error: > > gas/i386/intelbad.s:156: Error: operand type mismatch for `mov' > > doesn't show up. As I said - I do n

[Bug ld/12374] New: ld fails to convert global hidden symbols to local ones

2011-01-07 Thread jbeulich at novell dot com
http://sourceware.org/bugzilla/show_bug.cgi?id=12374 Summary: ld fails to convert global hidden symbols to local ones Product: binutils Version: 2.21 Status: NEW Severity: normal Priority: P2 Component: l

[Bug ld/12374] ld fails to convert global hidden symbols to local ones

2011-02-14 Thread jbeulich at novell dot com
http://sourceware.org/bugzilla/show_bug.cgi?id=12374 Jan Beulich changed: What|Removed |Added Status|NEW |RESOLVED Resolution|