https://bugs.kde.org/show_bug.cgi?id=390524
Bug ID: 390524
Summary: use of 0b prefix for binary constants
Product: valgrind
Version: 3.14 SVN
Platform: Other
OS: Linux
Status: UNCONFIRMED
Severity: normal
Priority: NOR
Component: vex
Assignee: jsew...@acm.org
Reporter: jeff.fro...@gmail.com
Target Milestone: ---
Was there a conscious decision to begin using 0b prefixes [more widely] in
3.14.0?
I'm trying to build 3.14.0 on/for an x86 linux box using gcc 4.1.2 (it's an old
FC7 distro that we're using for an embedded application). I pulled the 3.14.0
valgrind source from the repository using git, ran the autogen, followed by
"./configure prefix=$HOME/valgrind exec_prefix=$HOME/valgrind", and make.
The build chokes on a binary constant ("0b00010000") at line 1802 in
priv/guest_s390_toIR.c:
priv/guest_s390_toIR.c:1802:43: error: invalid suffix "b00010000" on integer
constant
3.13.0 builds fine (though I didn't use git to pull it -- I just used the
source tarball).
I noticed that there are uses of the "0b" prefix in 3.13.0, but that seems to
be limited to the ARM architectures (where presumably all the SDKs are
relatively new and support "0b" use).
Would it be possible to avoid use of "0b" in the x86 flavors?
--
You are receiving this mail because:
You are watching all bug changes.
