This is the mail archive of the
gcc-patches@gcc.gnu.org
mailing list for the GCC project.
Re: Is testing libgomp outside of the build tree supported?
- From: "Joseph S. Myers" <joseph at codesourcery dot com>
- To: Andrew Pinski <pinskia at gmail dot com>
- Cc: Diego Novillo <dnovillo at google dot com>, Ian Lance Taylor <iant at google dot com>, Paul Pluzhnikov <ppluzhnikov at google dot com>, gcc-patches <gcc-patches at gcc dot gnu dot org>, Brooks Moses <bmoses at google dot com>
- Date: Mon, 3 Feb 2014 23:52:48 +0000
- Subject: Re: Is testing libgomp outside of the build tree supported?
- Authentication-results: sourceware.org; auth=none
- References: <ye6qzjm8gjkb dot fsf at elbrus2 dot mtv dot corp dot google dot com> <CAKOQZ8yoBd=UgtpHTZKvvEeau8Cs_Y7LRTYBMRzxXLZNHEL3MQ at mail dot gmail dot com> <CAD_=9DTrRA9i5Hh9zZh8HD8+oUg_rdZi47fmo7T7GxdTUqTF-Q at mail dot gmail dot com> <CA+=Sn1=AD79VQqWZtht73Gb48b-QOREAefK4Wf_o6tEKnMtKOg at mail dot gmail dot com>
On Mon, 3 Feb 2014, Andrew Pinski wrote:
> On Mon, Feb 3, 2014 at 11:14 AM, Diego Novillo <dnovillo@google.com> wrote:
> > On Mon, Feb 3, 2014 at 2:11 PM, Ian Lance Taylor <iant@google.com> wrote:
> >
> >> If the presence of the build
> >> tree makes writing some tests significantly simpler, I think that is
> >> OK.
> >
> > I would like to discourage that. Testing an already installed GCC for
> > which no build tree exists is a very useful feature.
>
> I agree. Here at Cavium, we use the packaged up toolchain that comes
> from a RPM and test it so we are testing exactly what we ship out to
> our customers.
Similarly at Mentor.
--
Joseph S. Myers
joseph@codesourcery.com