This is the mail archive of the
gcc-bugs@gcc.gnu.org
mailing list for the GCC project.
[Bug c++/55619] [4.8 Regression] Chromium build fails with: error: memory input is not directly addressable
- From: "jakub at gcc dot gnu.org" <gcc-bugzilla at gcc dot gnu dot org>
- To: gcc-bugs at gcc dot gnu dot org
- Date: Thu, 20 Dec 2012 10:41:51 +0000
- Subject: [Bug c++/55619] [4.8 Regression] Chromium build fails with: error: memory input is not directly addressable
- Auto-submitted: auto-generated
- References: <bug-55619-4@http.gcc.gnu.org/bugzilla/>
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=55619
--- Comment #10 from Jakub Jelinek <jakub at gcc dot gnu.org> 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_parser_asm_operands): Remove CONVERT_P
argument, don't call default_function_array_conversion
nor c_fully_fold here.
(c_parser_asm_statement): Adjust callers.
* c-typeck.c (build_asm_expr): Call c_fully_fold on inputs
and outputs here, and call default_function_array_conversion
on inputs that don't need to be addressable.
* c-c++-common/pr55619.c: New test.
Added:
trunk/gcc/testsuite/c-c++-common/pr55619.c
Modified:
trunk/gcc/c/ChangeLog
trunk/gcc/c/c-parser.c
trunk/gcc/c/c-typeck.c
trunk/gcc/testsuite/ChangeLog