On December 8, 2017 4:26:05 AM GMT+01:00, Martin Sebor wrote:
>On 12/06/2017 11:45 PM, Richard Biener wrote:
>> On December 7, 2017 2:15:53 AM GMT+01:00, Martin Sebor
> wrote:
>>> On 12/06/2017 12:11 PM, Richard Biener wrote:
On December 6, 2017 6:38:11 PM GMT+01:00, Martin Sebor
>>> wrote:
On 12/06/2017 11:45 PM, Richard Biener wrote:
On December 7, 2017 2:15:53 AM GMT+01:00, Martin Sebor wrote:
On 12/06/2017 12:11 PM, Richard Biener wrote:
On December 6, 2017 6:38:11 PM GMT+01:00, Martin Sebor
wrote:
While testing a libstdc++ patch that relies on inlining to
expose a GCC lim
Snapshot gcc-7-20171207 is now available on
ftp://gcc.gnu.org/pub/gcc/snapshots/7-20171207/
and on various mirrors, see http://gcc.gnu.org/mirrors.html for details.
This snapshot has been generated from the GCC 7 SVN branch
with the following options: svn://gcc.gnu.org/svn/gcc/branches/gcc-7
On 07/12/17 15:17, Joseph Myers wrote:
On Thu, 7 Dec 2017, Thomas Preudhomme wrote:
That seems to go counter to the --prefix option of contrib/test_installed
which is meant to test a compiler at an arbitrary path. This suggest the
compiler is not expected to be in PATH or in any dejagnu configu
On Thu, 7 Dec 2017, Thomas Preudhomme wrote:
> That seems to go counter to the --prefix option of contrib/test_installed
> which is meant to test a compiler at an arbitrary path. This suggest the
> compiler is not expected to be in PATH or in any dejagnu configuration file.
> Seems most of the tes
Hi Joseph,
On 06/12/17 17:53, Joseph Myers wrote:
On Wed, 6 Dec 2017, Thomas Preudhomme wrote:
== problem ==
I'm not sure where is the proper place to fix this. Obviously setting
CC_FOR_TARGET in contrib/test_installed or when calling runtest manually would
work but I wonder if this would not
