[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
[Bug gold/22268] New: ld.gold accepts "foo = ~0xFF" in linker script whi
From: |
georgerim at gmail dot com |
Subject: |
[Bug gold/22268] New: ld.gold accepts "foo = ~0xFF" in linker script while ld.bfd - not. |
Date: |
Fri, 06 Oct 2017 11:48:39 +0000 |
https://sourceware.org/bugzilla/show_bug.cgi?id=22268
Bug ID: 22268
Summary: ld.gold accepts "foo = ~0xFF" in linker script while
ld.bfd - not.
Product: binutils
Version: 2.30 (HEAD)
Status: UNCONFIRMED
Severity: normal
Priority: P2
Component: gold
Assignee: ccoutant at gmail dot com
Reporter: georgerim at gmail dot com
CC: ian at airs dot com
Target Milestone: ---
I am using latest ld.gold built from sources:
GNU gold (GNU Binutils 2.29.51.20171006) 1.14
It accepts both two next scripts:
SECTIONS { . = 0x10000; foo = ~0xFF; }
SECTIONS { . = 0x10000; foo = ~ 0xFF; }
Though lb.bfd does not like first version, it reports:
"test.script:3: undefined symbol `~0xFF' referenced in expression"
It is not clear what is intentional behavior, as it not documented I think.
I opened bug for ld.bfd here:
https://sourceware.org/bugzilla/show_bug.cgi?id=22267
--
You are receiving this mail because:
You are on the CC list for the bug.
- [Bug gold/22268] New: ld.gold accepts "foo = ~0xFF" in linker script while ld.bfd - not.,
georgerim at gmail dot com <=