public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "markus at trippelsdorf dot de" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug tree-optimization/55619] New: [4.8 Regression] Chromium build fails with: error: memory input is not directly addressable
Date: Sat, 08 Dec 2012 07:47:00 -0000 [thread overview]
Message-ID: <bug-55619-4@http.gcc.gnu.org/bugzilla/> (raw)
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=55619
Bug #: 55619
Summary: [4.8 Regression] Chromium build fails with: error:
memory input is not directly addressable
Classification: Unclassified
Product: gcc
Version: 4.8.0
Status: UNCONFIRMED
Severity: normal
Priority: P3
Component: tree-optimization
AssignedTo: unassigned@gcc.gnu.org
ReportedBy: markus@trippelsdorf.de
On current trunk I get:
% c++ -c compare_posix.ii
third_party/libyuv/source/compare_posix.cc: In function ‘uint32
libyuv::HashDjb2_SSE41(const uint8*, int, uint32)’:
third_party/libyuv/source/compare_posix.cc:156:4: error: memory input 4 is not
directly addressable
third_party/libyuv/source/compare_posix.cc:156:4: error: memory input 5 is not
directly addressable
third_party/libyuv/source/compare_posix.cc:156:4: error: memory input 6 is not
directly addressable
third_party/libyuv/source/compare_posix.cc:156:4: error: memory input 7 is not
directly addressable
third_party/libyuv/source/compare_posix.cc:156:4: error: memory input 8 is not
directly addressable
%
<= gcc version 4.8.0 20121123 (experimental) (GCC) is OK
> gcc version 4.8.0 20121130 (experimental) (GCC) fails
next reply other threads:[~2012-12-08 7:47 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-12-08 7:47 markus at trippelsdorf dot de [this message]
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
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@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: link
Be 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).