[Bug ada/14435] New: Ada testsuite doesn't use the newly compiler

[Bug ada/14435] New: Ada testsuite doesn't use the newly compiler

[hjl at lucon dot org]

Ada testsuite log gives very little information. I got many

Running chapter a ...
/export/build/gnu/gcc-3.4/build-pentium4-
linux/gcc/testsuite/ada/acats/tests/a/a22006b.ada:
parse errors detected
/export/build/gnu/gcc-3.4/build-pentium4-
linux/gcc/testsuite/ada/acats/tests/a/a22006b.ada:
chop may not be successful
/export/build/gnu/gcc-3.4/build-pentium4-
linux/gcc/testsuite/ada/acats/tests/a/a22006b.ada:
error parsing offset info
no compilation units found
no source files written

on Linux/x86. To reproduce,

1. Build gcc 3.4 with ada.
2. Install gcc 3.4.
3. Replace gnat1 in the installed gcc 3.4 directory with a dummy shell
script which returns 1.
4. Run "make check-ada" in the gcc build direcory and watch massive failures.

It looks like Ada testsuite forgets to make sure the newly build Ada
compiler is used instead of the installed one.

-- 
           Summary: Ada testsuite doesn't use the newly compiler
           Product: gcc
           Version: 3.4.0
            Status: UNCONFIRMED
          Severity: normal
          Priority: P2
         Component: ada
        AssignedTo: unassigned at gcc dot gnu dot org
        ReportedBy: hjl at lucon dot org
                CC: gcc-bugs at gcc dot gnu dot org


http://gcc.gnu.org/bugzilla/show_bug.cgi?id=14435

[Bug ada/14435] Ada testsuite doesn't use the newly compiler

[charlet at gcc dot gnu dot org]

------- Additional Comments From charlet at gcc dot gnu dot org  2004-03-05 00:12 -------
This bug report is incomplete, here is what I get, as expected:

<<
                === acats support ===
Generating support files...gnatmake: "macrosub.adb" not found
**** Failed to compile macrosub
make: *** [check-gnat] Error 1
>>

Since the host gnatmake is screwed up, there's no way you can get past the
set up point.

So I suspect your problem is elsewhere.
The ACATS scripts make sure the compiler in the build directory is used
for compiling the ACATS tests, there's no doubt about it.

Putting this PR on hold for now.

Arno

-- 
           What    |Removed                     |Added
----------------------------------------------------------------------------
             Status|UNCONFIRMED                 |WAITING


http://gcc.gnu.org/bugzilla/show_bug.cgi?id=14435

[Bug ada/14435] Ada testsuite doesn't use the newly compiler

[hjl at lucon dot org]

------- Additional Comments From hjl at lucon dot org  2004-03-05 01:47 -------
Please make sure you DON'T use the installed gcc 3.4 to bootstrap gcc 3.4.
In my case, I am using RedHat EL 3. The system compiler is used to bootstrap
gcc 3.4. Changing gnat1 in the installed gcc 3.4 shouldn't affect host
gnatmake.

-- 
           What    |Removed                     |Added
----------------------------------------------------------------------------
             Status|WAITING                     |NEW
     Ever Confirmed|                            |1
   Last reconfirmed|0000-00-00 00:00:00         |2004-03-05 01:47:05
               date|                            |


http://gcc.gnu.org/bugzilla/show_bug.cgi?id=14435

[Bug driver/14435] [3.4 regression] GCC_EXEC_PREFIX does not work as expected

[charlet at gcc dot gnu dot org]

------- Additional Comments From charlet at gcc dot gnu dot org  2004-03-05 08:33 -------
It doesn't affect host gnatmake.

The issue here is really specific to gnatchop.
gnatmake uses the right compiler, as explained several times.

target gnatchop indeed uses a gnat1 in the default install dir
if there's one, which is because the GCC_EXEC_PREFIX environment
variable is broken in GCC: setting GCC_EXEC_PREFIX is no longer
doing the expected job of being equivalent to -Bxxxx

Note also that the documentation on GCC_EXEC_PREFIX is inconsistent and
unclear.

Requalifying this PR so that the behavior of GCC_EXEC_PREFIX is restored
and so that the ACATS test suite can use it, and remove the kludge
put in place to work around it, and which indeed does not work completely
with gnatchop as you reported.

Here are more info on GCC_EXEC_PREFIX being broken:

$ export GCC_EXEC_PREFIX=/home/charlet/cvs/gcc-obj/gcc/
$ gcc -v -c -x ada /dev/null
Reading specs from /home/charlet/cvs/gcc-obj/gcc/specs <- this part is fine
Configured with: ../gcc-head/configure [..]
gcc version 3.5.0 20040220 (experimental)
 /home/charlet/cvs/gcc-obj/install/libexec/gcc/i686-pc-linux-gnu/3.5.0/gnat1 -
quiet -dumpbase null.ada -mtune=pentiumpro /dev/null -o /tmp/ccIDh52n.s  <- this
part isn't, the wrong gnat1 is called

As you can see (and same for cc1), the wrong gnat1 is called.
Once this regression is fixed, it will be possible to clean up
the acats driver.

Arno

-- 
           What    |Removed                     |Added
----------------------------------------------------------------------------
          Component|ada                         |driver
            Summary|Ada testsuite doesn't use   |[3.4 regression]
                   |the newly compiler          |GCC_EXEC_PREFIX does not
                   |                            |work as expected


http://gcc.gnu.org/bugzilla/show_bug.cgi?id=14435

[Bug ada/14435] Ada's testsuite does not use the compiled compiler

[pinskia at gcc dot gnu dot org]

------- Additional Comments From pinskia at gcc dot gnu dot org  2004-03-16 01:54 -------
Actually it is because of the last paragraph in the docs:
In addition, the prefix is used in an unusual way in finding the directories to search for header files. For 
each of the standard directories whose name normally begins with /usr/local/lib/gcc (more precisely, 
with the value of GCC_INCLUDE_DIR), GCC tries replacing that beginning with the specified prefix to 
produce an alternate directory name. Thus, with -Bfoo/, GCC will search foo/bar where it would 
normally search /usr/local/lib/bar. These alternate directories are searched first; the standard 
directories come next. 
So you have use -B./ also.

-- 
           What    |Removed                     |Added
----------------------------------------------------------------------------
          Component|driver                      |ada
            Summary|[3.4 regression]            |Ada's testsuite does not use
                   |GCC_EXEC_PREFIX does not    |the compiled compiler
                   |work as expected            |


http://gcc.gnu.org/bugzilla/show_bug.cgi?id=14435

[Bug ada/14435] Ada's testsuite does not use the compiled compiler

[charlet at act-europe dot fr]

------- Additional Comments From charlet at act-europe dot fr  2004-03-16 08:43 -------
Subject: Re:  Ada's testsuite does not use the compiled compiler

> So you have use -B./ also.

And what if I can't ? This is really a regression in the behvior of
GCC_EXEC_PREFIX to me, in particular since part of the doc mentions that
GCC_EXEC_PREFIX is equivalent to -Bxxx, which is wrong if I understand your
comment correctly.

If you're right and GCC_EXEC_PREFIX always needs to be used with -B./ then
GCC_EXEC_PREFIX is useless and should be completely removed.

I'd rather see the old GCC_EXEC_PREFIX behavior restored.

Arno


-- 


http://gcc.gnu.org/bugzilla/show_bug.cgi?id=14435

[Bug ada/14435] gnatchop cannot use the compiled compiler in Ada's testsuite because of changed GCC_EXEC_PREFIX semantics

[charlet at gcc dot gnu dot org]

------- Additional Comments From charlet at gcc dot gnu dot org  2004-03-16 14:13 -------
Fixing the incorrect summary line.

Arno

-- 
           What    |Removed                     |Added
----------------------------------------------------------------------------
            Summary|Ada's testsuite does not use|gnatchop cannot use the
                   |the compiled compiler       |compiled compiler in Ada's
                   |                            |testsuite because of changed
                   |                            |GCC_EXEC_PREFIX semantics


http://gcc.gnu.org/bugzilla/show_bug.cgi?id=14435

[Bug ada/14435] gnatchop cannot use the compiled compiler in Ada's testsuite because of changed GCC_EXEC_PREFIX semantics

[charlet at gcc dot gnu dot org]

------- Additional Comments From charlet at gcc dot gnu dot org  2005-05-17 11:58 -------
Closing, as nobody seems to care about GCC_EXEC_PREFIX being broken.

Arno

-- 
           What    |Removed                     |Added
----------------------------------------------------------------------------
             Status|NEW                         |RESOLVED
         Resolution|                            |WONTFIX


http://gcc.gnu.org/bugzilla/show_bug.cgi?id=14435