On Thu, Jul 03, 2014 at 02:37:41PM +0200, Thomas Schwinge wrote:
> OK to document as follows?
>
> 2014-07-03 Jakub Jelinek
>
> libgomp/
> * testsuite/libgomp.fortran/fortran.exp: Explain
> gfortran-dg-runtest usage.
You wrote the patch, so put your name on it. Ok with that
Hi!
On Thu, 3 Jul 2014 13:09:57 +0200, Jakub Jelinek wrote:
> On Thu, Jul 03, 2014 at 01:06:48PM +0200, Thomas Schwinge wrote:
> > On Thu, 3 Jul 2014 12:58:32 +0200, Jakub Jelinek wrote:
> > > On Thu, Jul 03, 2014 at 12:54:32PM +0200, Thomas Schwinge wrote:
> > > > Thanks Janis and Mikael for yo
On Thu, Jul 03, 2014 at 01:06:48PM +0200, Thomas Schwinge wrote:
> On Thu, 3 Jul 2014 12:58:32 +0200, Jakub Jelinek wrote:
> > On Thu, Jul 03, 2014 at 12:54:32PM +0200, Thomas Schwinge wrote:
> > > Thanks Janis and Mikael for your replies (nearly a year ago...), but
> > > still my questions remain
Hi!
On Thu, 3 Jul 2014 12:58:32 +0200, Jakub Jelinek wrote:
> On Thu, Jul 03, 2014 at 12:54:32PM +0200, Thomas Schwinge wrote:
> > Thanks Janis and Mikael for your replies (nearly a year ago...), but
> > still my questions remain to be answered: in my understanding, the
> > libgomp testsuite is n
On Thu, Jul 03, 2014 at 12:54:32PM +0200, Thomas Schwinge wrote:
> Thanks Janis and Mikael for your replies (nearly a year ago...), but
> still my questions remain to be answered: in my understanding, the
> libgomp testsuite is not the place for compiler torture testing
> (different optimization fl
Hi!
On Tue, 13 Aug 2013 13:06:30 +0200, I wrote:
> I noticed something strange in the libgomp testresults (but not
> necessarily specific to libgomp): an "arbitrary" set of the Fortran
> execution tests are run just for -O, and others for each of the full set
> of torture options: -O0, -O1, -O2, a
