This is the mail archive of the gcc-patches@gcc.gnu.org mailing list for the GCC project.


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]
Other format: [Raw text]

Re: new abi file for x86_64-linux-gnu


>I think everything has settled down - how shall we continue now?

There are two things.

1) Right now, if there is no abi file, the output looks like:

Baseline file doesn't exist.
Try 'make new-abi-baseline' to create it.
make[4]: [baseline_symbols] Error 1 (ignored)
make[4]: [check-abi] Error 1 (ignored)

Which seems to be confusing people. See:

http://gcc.gnu.org/ml/gcc/2003-06/msg01837.html

it would be nice if this didn't error out, but instead just printed out
the message about creating a new baseline file, and then silently
skipped the check-abi rule. I don't have time to do this, but if
somebody else does I'd appreciate it.

2) Updating the baseline files to 3.3.0 versions. 

First, the error where the "extract_symvers" script creates the current
baseline symbols file without sorting it needs to be fixed. As it
stands, the created file looks like it's got all kinds of difference
from the 3.2.0 baseline, just because it's not sorted. This needs to be
fixed.

The updates should proceed as follows. If there is a 3.2.0 baseline,
then get the gcc-3.3.0 sources, compile them, and do check-abi. If there
are no incompatible symbols in the results, you can use the new baseline
file as the update. (Note that the new-abi-baseline rule does the same
thing.)

If there is no 3.2.0 baseline file for a new target, it would be nice if
it could be generated, then compared against the 3.3.0 baseline.
However, it looks like this may be difficult or impossible for some
targets (powerpc64?). So, I don't know what to do in this case. I guess
just use the 3.3.0 generated file.

Thoughts?

-benjamin



Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]