On 12 Jan 14:30, Jeff Law wrote:
> On 01/11/15 12:26, Ilya Verbin wrote:
> >On 09 Jan 10:29, Thomas Schwinge wrote:
> >>As this was the only use of ENABLE_LTO in the testsuite, I suggest to
> >>also remove it from the gcc/Makefile.in:site.exp rule.
> >
> >Done.
> >Here is an updated and retested pa
On 01/11/15 12:26, Ilya Verbin wrote:
On 09 Jan 10:29, Thomas Schwinge wrote:
As this was the only use of ENABLE_LTO in the testsuite, I suggest to
also remove it from the gcc/Makefile.in:site.exp rule.
Done.
Here is an updated and retested patch. OK for trunk?
gcc/
* Makefile.in (s
On 09 Jan 10:29, Thomas Schwinge wrote:
> As this was the only use of ENABLE_LTO in the testsuite, I suggest to
> also remove it from the gcc/Makefile.in:site.exp rule.
Done.
Here is an updated and retested patch. OK for trunk?
gcc/
* Makefile.in (site.exp): Do not set ENABLE_LTO.
gcc/t
Hi!
On Fri, 9 Jan 2015 03:40:29 +0300, Ilya Verbin wrote:
> Currently check_effective_target_lto properly works only in gcc/testsuite/
> dir,
> since it checks for ENABLE_LTO, which is defined in gcc/configure.ac.
> But it doesn't work in other subdirectories, e.g. in libgomp/testsuite/.
> This
Hi!
Currently check_effective_target_lto properly works only in gcc/testsuite/ dir,
since it checks for ENABLE_LTO, which is defined in gcc/configure.ac.
But it doesn't work in other subdirectories, e.g. in libgomp/testsuite/.
This patch fixes it.
make check and check-target-libgomp passed with/wi
