** Changed in: gcc-linaro-tracking
Status: Fix Committed => Fix Released
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/675347
Title:
volatile int causes inline assembly build failure
To mana
** Branch linked: lp:debian/gnat-4.6
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/675347
Title:
volatile int causes inline assembly build failure
To manage notifications about this bug go to:
http
fixed in the gcc-4.6 package (oneiric, and unstable)
** Changed in: gcc-4.6 (Ubuntu Natty)
Status: New => Invalid
** Changed in: gcc-4.6 (Ubuntu)
Status: New => Fix Released
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubun
Looking at the comments the patch has landed in mainline but does not
exist in GCC 4.6.0.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/675347
Title:
volatile int causes inline assembly build failur
** Bug watch added: Debian Bug tracker #625825
http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=625825
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/675347
Title:
volatile int causes inline assem
On 05/06/2011 01:09 PM, Andrew Stubbs wrote:
> The patch was committed here:
>
> http://bazaar.launchpad.net/~linaro-toolchain-dev/gcc-
> linaro/4.6/revision/106731
>
> Does you compiler not have that?
no, currently using the fsf branch. and apparently not only seen on
Ubuntu:
http://bugs.debian
The patch was committed here:
http://bazaar.launchpad.net/~linaro-toolchain-dev/gcc-
linaro/4.6/revision/106731
Does you compiler not have that?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/675347
For the error see: https://launchpadlibrarian.net/71179182
/buildlog_ubuntu-oneiric-armel.doxygen_1.7.4-1_FAILEDTOBUILD.txt.gz
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/675347
Title:
volatile in
The patch seems not applied in gcc-4.6 that we use?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/675347
Title:
volatile int causes inline assembly build failure
--
ubuntu-bugs mailing list
ubuntu
I can't reproduce the problem with the original testcase. Is this a new
problem?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/675347
Title:
volatile int causes inline assembly build failure
--
ub
now seen again with gcc-4.6 in oneiric
** Also affects: gcc-4.6 (Ubuntu)
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/675347
Title:
volatile int causes
** Changed in: gcc-linaro
Status: Fix Committed => Fix Released
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/675347
Title:
volatile int causes inline assembly build failure
--
ubuntu-bugs
The fix was committed to Linaro GCC yesterday.
Related: lp:gcc-linaro/4.5,revno=99493
** Changed in: gcc-linaro
Status: In Progress => Fix Committed
** Changed in: gcc-linaro
Milestone: None => 4.5-2011.04-0
--
You received this bug notification because you are a member of Ubuntu
Bu
Andrew, could you check the status of this ticket please?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/675347
Title:
volatile int causes inline assembly build failure
--
ubuntu-bugs mailing list
** Branch linked: lp:gcc-linaro
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/675347
Title:
volatile int causes inline assembly build failure
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.c
Oops, bad syntax ...
Related: lp:gcc-linaro/4.6,revno=106731
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/675347
Title:
volatile int causes inline assembly build failure
--
ubuntu-bugs mailing l
The 4.6 version is ok though:
Related: gcc-linaro/4.6,revno=106731
** Also affects: gcc-linaro-tracking
Importance: Undecided
Status: New
** Changed in: gcc-linaro-tracking
Status: New => Fix Committed
** Changed in: gcc-linaro-tracking
Milestone: None => 4.7.0
** Changed
** Branch linked: lp:gcc-linaro/4.6
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/675347
Title:
volatile int causes inline assembly build failure
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubun
My backport of this patch appears to cause some test regressions caused
by a compiler segmentation fault.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/675347
Title:
volatile int causes inline assem
** Branch linked: lp:debian/gcc-4.5
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/675347
Title:
volatile int causes inline assembly build failure
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubun
This bug was fixed in the package gcc-4.5 - 4.5.2-7ubuntu1
---
gcc-4.5 (4.5.2-7ubuntu1) natty; urgency=low
* Merge with Debian.
gcc-4.5 (4.5.2-7) unstable; urgency=low
* Update to SVN 20110323 (r171351) from the gcc-4_5-branch.
- Fix PR c++/47125, PR fortran/47348, PR libstd
** Branch linked: lp:~ams-codesourcery/gcc-linaro/lp675347
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/675347
Title:
volatile int causes inline assembly build failure
--
ubuntu-bugs mailing list
Julian has now committed the patch upstream:
http://gcc.gnu.org/ml/gcc-patches/2011-03/msg01477.html
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/675347
Title:
volatile int causes inline assembly
** Changed in: gcc-4.5 (Ubuntu Natty)
Milestone: ubuntu-11.04-beta-1 => None
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/675347
Title:
volatile int causes inline assembly build failure
--
ub
** Changed in: gcc-linaro
Assignee: Julian Brown (julian-codesourcery) => Andrew Stubbs
(ams-codesourcery)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/675347
Title:
volatile int causes inlin
Still not landed upstream. Andrew, could you ask Julian to ping this
again or push it upstream yourself?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/675347
Title:
volatile int causes inline assem
** Changed in: gcc-4.5 (Ubuntu Natty)
Milestone: natty-alpha-3 => ubuntu-11.04-beta-1
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/675347
Title:
volatile int causes inline assembly build failur
Still not landed upstream.
** Changed in: gcc-linaro
Milestone: 4.5-2011.02-0 => None
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/675347
Title:
volatile int causes inline assembly build failu
** Branch linked: lp:~ams-codesourcery/gcc-linaro/lp675347-4.6
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/675347
Title:
volatile int causes inline assembly build failure
--
ubuntu-bugs mailing
Pushing to alpha-3, since the problem has been worked around as Matthias
notes in comment 36.
** Changed in: gcc-4.5 (Ubuntu Natty)
Milestone: natty-alpha-2 => natty-alpha-3
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://
the current gcc-4.5 does revert the change from comment #26
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/675347
Title:
volatile int causes inline assembly build failure
--
ubuntu-bugs mailing lis
Please ensure that qt4-x11 is test built and verified with any fixes.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/675347
Title:
volatile int causes inline assembly build failure
--
ubuntu-bugs m
** Changed in: gcc-linaro
Milestone: 4.5-2011.01-0 => 4.5-2011.02-0
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/675347
Title:
volatile int causes inline assembly build failure
--
ubuntu-bugs
Julian has pinged this.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/675347
Title:
volatile int causes inline assembly build failure
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https
Oops. Saw another volatile bitfields patch and mis-read it as fixing
this. Marked back as in progress.
** Changed in: gcc-linaro
Status: In Progress => Fix Committed
** Changed in: gcc-linaro
Status: Fix Committed => In Progress
** Changed in: gcc-linaro
Milestone: 4.5-2010.1
** Changed in: gcc-4.5 (Ubuntu Natty)
Assignee: (unassigned) => Canonical Foundations Team
(canonical-foundations)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/675347
Title:
volatile int caus
No. That's caused by removing implicit-it=thumb from the default gcc
config. There is another bug about that.
--
volatile int causes inline assembly build failure
https://bugs.launchpad.net/bugs/675347
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed
https://bugs.launchpad.net/bugs/682742 looks like similar issue
--
volatile int causes inline assembly build failure
https://bugs.launchpad.net/bugs/675347
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
ubun
I'm pretty sure we're dealing with a compiler regression here: note that
there isn't actually any usage of bitfields in the test case given
(rather, it uses a volatile int), it just so happened that the code to
implement -fstrict-volatile-bitfields caused a particular code path to
be erroneously ex
@Julian
My 2c: since ISO C says volatile bitfields are wrong, then if any code
needs -fno-strict-volatile-bitfields to build, then either that code is
wrong (which is not obviously true in this case--- but if is it true I
would like to understand how so we can avoid it), or ... the compiler is
wro
Using 'Q' (as in the message I posted to the GCC list) seems to work,
but still gives a warning rather than an error. That might be an
acceptable workaround, I guess. (It's probably the correct thing to do
anyway.)
--
volatile int causes inline assembly build failure
https://bugs.launchpad.net/bu
I notice that _q_value is referenced twice in the constraints.
Can we get rid of the reference causing the problem, i.e.:
asm volatile("0:\n"
"ldrex %[newValue], [%[_q_value]]\n"
"sub %[newValue], %[newValue], #1\n"
"strex %[result], %[newVal
The simplest way to achieve that at present is probably for Ubuntu
(locally) to revert the patch:
2010-10-26 Jie Zhang
Issue #1259
Backport from mainline:
gcc/
2010-10-26 Jie Zhang
* stor-layout.c (layout_decl): Use the field's type to
dete
Could the g++ default be changed in gcc-defaults for now so we could get on
with things while the patch is being sorted?
--
volatile int causes inline assembly build failure
https://bugs.launchpad.net/bugs/675347
You received this bug notification because you are a member of Ubuntu
Bugs, which i
adding "-fstrict-volatile-bitfields" would need touching every package
again, which is not better. lets wait for feedback on the GCC fix.
--
volatile int causes inline assembly build failure
https://bugs.launchpad.net/bugs/675347
You received this bug notification because you are a member of Ubun
Scott, Matthias: there's a work around by setting -fno-strict-volatile-
bitfields but, due to this being inline assembler, the flag needs to be
the default for anything that includes qatomic.h.
-fstrict-volatile-bitfields was added in 2010.11 so there's no loss in
turning it off. Is there a way o
Incidentally I'd like to hear the upstream opinion on this patch before
we apply it to our 4.5 tree, and especially before we deploy software
using it.
Thanks,
Julian
--
volatile int causes inline assembly build failure
https://bugs.launchpad.net/bugs/675347
You received this bug notification b
So we'll just leave Qt/KDE broken for another month? That doesn't sound so
great either.
--
volatile int causes inline assembly build failure
https://bugs.launchpad.net/bugs/675347
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ub
please no compiler upload before alpha-1 is out
** Changed in: gcc-4.5 (Ubuntu Natty)
Milestone: natty-alpha-1 => natty-alpha-2
--
volatile int causes inline assembly build failure
https://bugs.launchpad.net/bugs/675347
You received this bug notification because you are a member of Ubuntu
Bu
Patch posted upstream:
http://gcc.gnu.org/ml/gcc-patches/2010-11/msg02245.html
--
volatile int causes inline assembly build failure
https://bugs.launchpad.net/bugs/675347
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs m
** Changed in: gcc-linaro
Status: Confirmed => In Progress
--
volatile int causes inline assembly build failure
https://bugs.launchpad.net/bugs/675347
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
ub
** Changed in: gcc-linaro
Status: New => Confirmed
--
volatile int causes inline assembly build failure
https://bugs.launchpad.net/bugs/675347
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
ubuntu-bug
The build is past where it worked before, so I'll call this progress.
--
volatile int causes inline assembly build failure
https://bugs.launchpad.net/bugs/675347
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing lis
Building now. I should know if the work around does it in an hour.
--
volatile int causes inline assembly build failure
https://bugs.launchpad.net/bugs/675347
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
u
Sure. I'll try it again with no icecc.
--
volatile int causes inline assembly build failure
https://bugs.launchpad.net/bugs/675347
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
OK, looks like you're using a self-built GCC. The reference to the
system G++ (/usr/bin/g++) for COLLECT_GCC is interesting: that might
suggest a possible misconfiguration, and/or that the wrong binary is
still being picked up for some phase of compilation, for some reason.
Maybe try one of the fo
Just to be sure, I reran the build in the same chroot without the change
and got the same errors such as:
../../include/QtCore/../../src/corelib/arch/qatomic_armv6.h:119:35: error:
output number 2 not directly addressable
../../include/QtCore/../../src/corelib/arch/qatomic_armv6.h:119:35: warnin
# which g++
/usr/lib/icecc/bin/g++
r...@kubuntu-efikamx01:~/qt4-x11-4.7.1# /usr/lib/icecc/bin/g++ -v
Using built-in specs.
COLLECT_GCC=/usr/bin/g++
COLLECT_LTO_WRAPPER=/usr/lib/gcc/arm-linux-gnueabi/4.5.2/lto-wrapper
Target: arm-linux-gnueabi
Configured with: ../src/configure -v --with-pkgversion='
Your QT build must be picking up the wrong compiler:
mavis% g++-4.5 -O2 -save-temps -mfpu=neon -c atomic.cc
atomic.cc: In function 'int foo(QBasicAtomicInt&)':
atomic.cc:25:35: error: output number 2 not directly addressable
atomic.cc:25:35: warning: use of memory input without lvalue in asm oper
Yes. gcc-4.5 hasn't changed.
--
volatile int causes inline assembly build failure
https://bugs.launchpad.net/bugs/675347
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://li
Oh, that's really strange. Are you sure you're using the same G++
version which was previously failing with the inline-asm error?
--
volatile int causes inline assembly build failure
https://bugs.launchpad.net/bugs/675347
You received this bug notification because you are a member of Ubuntu
Bugs,
make[2]: Entering directory `/tmp/buildd/qt4-x11-4.7.1/qmake'
g++ -c -o project.o -pipe -DQMAKE_OPENSOURCE_EDITION -O2
-fno-strict-volatile-bitfields -fno-strict-volatile-bitfields -I. -Igenerators
-Igenerators/unix -Igenerators/win32 -Igenerators/mac -Igenerators/symbian
-I/tmp/buildd/qt4-x11-4
I have a test build in progress to try this.
--
volatile int causes inline assembly build failure
https://bugs.launchpad.net/bugs/675347
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubunt
I've not found a fix for this yet, but I think I have a workaround.
Could you try compiling with "-fno-strict-volatile-bitfields" and let me
know how you get on, please?
Thanks,
Julian
--
volatile int causes inline assembly build failure
https://bugs.launchpad.net/bugs/675347
You received this
Confirmed still a problem with qt4-x11 4.7.1 uploaded to Natty today.
--
volatile int causes inline assembly build failure
https://bugs.launchpad.net/bugs/675347
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing lis
** Tags removed: patch
--
volatile int causes inline assembly build failure
https://bugs.launchpad.net/bugs/675347
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ub
FAOD, we don't yet have a patch to fix this issue, do we?
--
volatile int causes inline assembly build failure
https://bugs.launchpad.net/bugs/675347
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
ubuntu-bug
** Tags added: patch
--
volatile int causes inline assembly build failure
https://bugs.launchpad.net/bugs/675347
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubun
Confirmed this as a regression in Ubuntu's gcc-4.5 4.5.1-10ubuntu1
(which uses Linaro's 2010.11). I'm currently building with
4.5.1-9ubuntu1 (which contains 2010.10) and am wll past where the newer
one fails.
** Changed in: gcc-4.5 (Ubuntu Natty)
Status: New => Confirmed
--
volatile int
This regression is blocking progress on getting Qt/KDE built on arm.
** Also affects: gcc-4.5 (Ubuntu)
Importance: Undecided
Status: New
** Changed in: gcc-4.5 (Ubuntu)
Importance: Undecided => High
** Also affects: gcc-4.5 (Ubuntu Natty)
Importance: High
Status: New
** C
70 matches
Mail list logo
