[Bug tree-optimization/55619] New: [4.8 Regression] Chromium build fails with: error: memory input is not directly addressable
markus at trippelsdorf dot de
gcc-bugzilla@gcc.gnu.org
Sat Dec 8 07:47:00 GMT 2012
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
More information about the Gcc-bugs
mailing list