[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
[Bug gas/31343] New: MIPS: correct behavior of branch to an imm?
From: |
syq at debian dot org |
Subject: |
[Bug gas/31343] New: MIPS: correct behavior of branch to an imm? |
Date: |
Tue, 06 Feb 2024 08:58:30 +0000 |
https://sourceware.org/bugzilla/show_bug.cgi?id=31343
Bug ID: 31343
Summary: MIPS: correct behavior of branch to an imm?
Product: binutils
Version: unspecified
Status: NEW
Severity: normal
Priority: P2
Component: gas
Assignee: unassigned at sourceware dot org
Reporter: syq at debian dot org
Target Milestone: ---
Some code like:
b (0)
generates the binary like:
00000000 <.text>:
0: 1000ffff b 0x0
0: R_MIPS_PC16 *ABS*
4: 00000000 nop
It will cause something wrong during runtime, normally,
jump to an address like 0xABCD0000.
https://github.com/llvm/llvm-project/issues/67951
Should we just emit an error for the asm code like this, or
emit binary without relocations?
How should we treat the IMM: may be how many bytes?
--
You are receiving this mail because:
You are on the CC list for the bug.
- [Bug gas/31343] New: MIPS: correct behavior of branch to an imm?,
syq at debian dot org <=
- [Bug gas/31343] MIPS: correct behavior of branch to an imm?, syq at debian dot org, 2024/02/06
- [Bug gas/31343] MIPS: correct behavior of branch to an imm?, macro at orcam dot me.uk, 2024/02/06
- [Bug gas/31343] MIPS: correct behavior of branch to an imm?, syq at debian dot org, 2024/02/06
- [Bug gas/31343] MIPS: correct behavior of branch to an imm?, syq at debian dot org, 2024/02/06
- [Bug gas/31343] MIPS: correct behavior of branch to an imm?, macro at orcam dot me.uk, 2024/02/06