gcc and qt bug

[macau]

i try native compile some qt apps on my tegra device, and catch gcc bug:
$this->bbcode_second_pass_code('', ' /usr/include/QtCore/qatomic_arm.h:232:35: error: output number 1 not directly addressable. ')
workaround and patch: http://gcc.gnu.org/ml/gcc-patches/2011-03/msg01477.html
seems our gcc 4.6.1 dont have thise pach

edit: also we have qt bug with same poblem. workaround and patches: http://lists.fedoraproject.org/pipermai ... 01964.html
http://fedoraproject.org/wiki/Architect ... age_status many other pathes and workarounds

[kmihelich]

You can also just add -fno-strict-volatile-bitfields to your CXXFLAGS.

[macau]

sure, but i think that thise bug must be fixed. i think that this patch not in apstream bks some of gcc mantainers dont have arm device

[WarheadsSE]

$this->bbcode_second_pass_quote('macau', 's')ure, but i think that this bug must be fixed. i think that this patch is not in upstream because some of the gcc mantainers dont have an arm device

[macau]

sorry for my english

[WarheadsSE]

To be honest macau, it's not your English in any particular sense I made those corrections for but because I take anyone with severe misuse of a language. While one can often see horrid examples of the use of any language with shortenings, misspellings, etc - things like 'bks' standing in for 'because' set me off a bit due to it being totally lacking in substance to the meaning of the real word.

Don't take personal offense, it was a matter of correcting it where I could

[kmihelich]

There have been many long discussions about this particular issue since GCC 4.6 was released earlier this year. What it boiled down to, if I remember right, was that it's not a bug in GCC but rather a bug in how Qt and other affected programs are written. As it's only a problem with one particular architecture in one particular set of programs, the GCC team does not see this as a bug or regression.

I would be willing to add the patch in to our GCC just so that I don't need the CXXFLAGS switch to build, I just never found that particular patch before. I'll have to run some tests to be sure it builds fine, however.

[WarheadsSE]

Can we not simply use the cxxflags in our PKGBUILD to get it fixed?

[kmihelich]

That's what I do now to get around the issue. If I patch it in GCC then I don't need to worry about modifying PKGBUILDs for the sole purpose of redefining CXXFLAGS.

[macau]

$this->bbcode_second_pass_quote('WarheadsSE', 'C')an we not simply use the cxxflags in our PKGBUILD to get it fixed?