This is the mail archive of the gcc-patches@gcc.gnu.org mailing list for the GCC project.


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]
Other format: [Raw text]

Re: [PATCH] Fix PR54702 and LTO bootstrap (for me)


On Mon, 14 Oct 2013, Mike Stump wrote:

> On Sep 25, 2012, at 8:00 AM, Richard Guenther <rguenther@suse.de> wrote:
> > 2012-09-25  Richard Guenther  <rguenther@suse.de>
> > 
> > 	PR lto/54625
> > 	* lto-symtab.c (lto_symtab_merge_cgraph_nodes_1): Do not merge
> > 	cgraph nodes for builtins.
> > 
> > 	* gcc.dg/lto/pr54702_0.c: New testcase.
> > 	* gcc.dg/lto/pr54702_1.c: Likewise.
> > 	* gcc.dg/lto/pr54625-1_0.c: Likewise.
> > 	* gcc.dg/lto/pr54625-1_1.C: Likewise.
> > 	* gcc.dg/lto/pr54625-2_0.c: Likewise.
> > 	* gcc.dg/lto/pr54625-2_1.C: Likewise.
> 
> 
> xgcc: error: /home/mrs/wg/gcc/gcc/testsuite/gcc.dg/lto/pr54625-2_1.C: C++ compiler not installed on this system
> 
> FAIL: gcc.dg/lto/pr54625-2 c_lto_pr54625-2_1.o assemble, -O2 -flto -fuse-linker-plugin
> 
> shouldn't C++ testcases go into the C++ testsuite?

Well ... this is a mixed C / C++ testcase (see the other file 
participating, gcc.dg/lto/pr54625-2_0.c).  The C testsuite is the only
one where the driver switches languages based on the file ending.

Hmm, it seems at least the fortran frontend knows how to mix fortran
and C.

So if you really did not build the C++ compiler then we need, at least
for lto.exp, a way to say dg-require-c++-frontend in the main file
(thats the _0 one).  Of course lto.exp misses a lot of other useful
stuff ;)

Btw, can we end up with the C frontend not built?

Richard.


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]