[Bug c++/55619] [4.8 Regression] Chromium build fails with: error: memory input is not directly addressable

2012-12-20 Thread jakub at gcc dot gnu.org
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=55619 --- Comment #10 from Jakub Jelinek 2012-12-20 10:41:51 UTC --- Author: jakub Date: Thu Dec 20 10:41:47 2012 New Revision: 194631 URL: http://gcc.gnu.org/viewcvs?root=gcc&view=rev&rev=194631 Log: PR c++/55619 * c-parser.c (c_p

[Bug c++/55619] [4.8 Regression] Chromium build fails with: error: memory input is not directly addressable

2012-12-11 Thread jakub at gcc dot gnu.org
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=55619 Jakub Jelinek changed: What|Removed |Added Status|UNCONFIRMED |RESOLVED Resolution|

[Bug c++/55619] [4.8 Regression] Chromium build fails with: error: memory input is not directly addressable

2012-12-11 Thread jakub at gcc dot gnu.org
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=55619 --- Comment #8 from Jakub Jelinek 2012-12-11 16:51:31 UTC --- Author: jakub Date: Tue Dec 11 16:51:16 2012 New Revision: 194404 URL: http://gcc.gnu.org/viewcvs?root=gcc&view=rev&rev=194404 Log: PR c++/55619 * semantics.c (fin

[Bug c++/55619] [4.8 Regression] Chromium build fails with: error: memory input is not directly addressable

2012-12-10 Thread jakub at gcc dot gnu.org
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=55619 --- Comment #7 from Jakub Jelinek 2012-12-10 14:48:00 UTC --- Created attachment 28913 --> http://gcc.gnu.org/bugzilla/attachment.cgi?id=28913 gcc48-pr55619.patch Here is (untested) patch I had in mind. But perhaps we'd need to also

[Bug c++/55619] [4.8 Regression] Chromium build fails with: error: memory input is not directly addressable

2012-12-10 Thread jakub at gcc dot gnu.org
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=55619 Jakub Jelinek changed: What|Removed |Added CC||jakub at gcc dot gnu.org,

[Bug c++/55619] [4.8 Regression] Chromium build fails with: error: memory input is not directly addressable

2012-12-10 Thread rguenth at gcc dot gnu.org
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=55619 Richard Biener changed: What|Removed |Added Target Milestone|--- |4.8.0

[Bug c++/55619] [4.8 Regression] Chromium build fails with: error: memory input is not directly addressable

2012-12-08 Thread glisse at gcc dot gnu.org
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=55619 --- Comment #5 from Marc Glisse 2012-12-08 08:49:35 UTC --- Indeed I got it down to this code, which fails just the same with an int instead of a vector. I didn't know it was forbidden to pass constants with the "m" constraint, I thought g

[Bug c++/55619] [4.8 Regression] Chromium build fails with: error: memory input is not directly addressable

2012-12-08 Thread pinskia at gcc dot gnu.org
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=55619 --- Comment #4 from Andrew Pinski 2012-12-08 08:29:53 UTC --- I think it is obvious what is happening. The c++ front-end is propagating the const vector. Does a const int cause a similar issue if so the inline-asm is buggy i think.

[Bug c++/55619] [4.8 Regression] Chromium build fails with: error: memory input is not directly addressable

2012-12-08 Thread markus at trippelsdorf dot de
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=55619 Markus Trippelsdorf changed: What|Removed |Added CC||glisse at gcc dot gnu.org