public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "glisse at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug c++/55619] [4.8 Regression] Chromium build fails with: error: memory input is not directly addressable Date: Sat, 08 Dec 2012 08:49:00 -0000 [thread overview] Message-ID: <bug-55619-4-XjzZ3zTrDD@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-55619-4@http.gcc.gnu.org/bugzilla/> http://gcc.gnu.org/bugzilla/show_bug.cgi?id=55619 --- Comment #5 from Marc Glisse <glisse at gcc dot gnu.org> 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 gcc would manage that somehow. What is the appropriate x86 constraint for a vector constant? "C" doesn't seem to work. typedef unsigned __attribute__((vector_size(16))) uvec32; static const uvec32 C = { 0x92d9e201, 0, 0, 0 }; //static const unsigned C = 0x92d9e201; void f() { asm volatile ( "" : : "m"(C)); }
next prev parent reply other threads:[~2012-12-08 8:49 UTC|newest] Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top 2012-12-08 7:47 [Bug tree-optimization/55619] New: " markus at trippelsdorf dot de 2012-12-08 7:48 ` [Bug tree-optimization/55619] " markus at trippelsdorf dot de 2012-12-08 8:06 ` pinskia at gcc dot gnu.org 2012-12-08 8:19 ` [Bug c++/55619] " markus at trippelsdorf dot de 2012-12-08 8:30 ` pinskia at gcc dot gnu.org 2012-12-08 8:49 ` glisse at gcc dot gnu.org [this message] 2012-12-10 9:53 ` rguenth at gcc dot gnu.org 2012-12-10 10:51 ` jakub at gcc dot gnu.org 2012-12-10 14:48 ` jakub at gcc dot gnu.org 2012-12-11 16:52 ` jakub at gcc dot gnu.org 2012-12-11 16:54 ` jakub at gcc dot gnu.org 2012-12-20 10:42 ` jakub at gcc dot gnu.org
Reply instructions: You may reply publicly to this message via plain-text email using any one of the following methods: * Save the following mbox file, import it into your mail client, and reply-to-all from there: mbox Avoid top-posting and favor interleaved quoting: https://en.wikipedia.org/wiki/Posting_style#Interleaved_style * Reply using the --to, --cc, and --in-reply-to switches of git-send-email(1): git send-email \ --in-reply-to=bug-55619-4-XjzZ3zTrDD@http.gcc.gnu.org/bugzilla/ \ --to=gcc-bugzilla@gcc.gnu.org \ --cc=gcc-bugs@gcc.gnu.org \ /path/to/YOUR_REPLY https://kernel.org/pub/software/scm/git/docs/git-send-email.html * If your mail client supports setting the In-Reply-To header via mailto: links, try the mailto: linkBe sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions for how to clone and mirror all data and code used for this inbox; as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).