Notes |
|
(0032608)
|
Brad King
|
2013-03-13 13:20
|
|
According to the xlc man page -qpic is the default:
-qpic[={small|large}] | -qnopic
...
Default: -qpic=small |
|
|
(0032609)
|
Kevin Burge
|
2013-03-13 13:32
|
|
Are you sure that doesn't just mean that the default for -qpic is -qpic=small? Otherwise, what would be the point of the option if ALL object files were created with pic? |
|
|
(0032611)
|
Brad King
|
2013-03-13 13:48
|
|
|
|
(0032612)
|
Brad King
|
2013-03-13 13:51
|
|
|
|
(0032613)
|
Kevin Burge
|
2013-03-13 14:11
|
|
Brad, thanks for looking into this. I admit that it looks like you are correct. If I run /usr/vacpp/bin/xlc, it in fact does show:
-qpic[={small|large}] | -qnopic
Generates position-independent code (pic). Specify
-qpic=small if the Global Offset Table in 32-bit
mode or Table of Contents in 64-bit mode must be 64
Kb or smaller, or -qpic=large if it can be larger
than 64 Kb.
Default: -qpic=small
But, using this very same vacpp, when I try:
/usr/vacpp/bin/xlc -qnopic mytest.c -c -o mytest.o
1506-173 (W) Option -qnopic is not valid. Enter xlc for list of valid options.
So, that does throw the documentation into question a bit. You can close this. We'll just do whatever we need to do. |
|
|
(0032614)
|
Brad King
|
2013-03-13 14:21
|
|
Re 0014010:0032613: The reason -qnopic does not work is probably due to the "When -q64 is in effect, -qpic is enabled and cannot be disabled" rule in the documentation linked in 0014010:0032611.
Does the patch in 0014010:0032612 solve this for you? |
|
|
(0032615)
|
Kevin Burge
|
2013-03-13 14:42
|
|
I tried -qnopic with and without -q32. I has the same warning.
We're trying your change, but with -qpic=large. We also added the -qpic=large to the shared library create flags, since you need it there also if you are explicitly stating the value (small|large).
It will be hours before the build will complete. I'll follow up later. |
|
|
(0032616)
|
Brad King
|
2013-03-13 15:16
|
|
|
|
(0032617)
|
Kevin Burge
|
2013-03-13 15:24
|
|
|
|
(0032632)
|
Brad King
|
2013-03-14 13:37
|
|
The change in 0014010:0032612 is now in master and will be in 2.8.11.
This resolves the issue as reported. Whether your particular project needs a special value for the flag is a separate discussion.
|
|
|
(0034006)
|
Robert Maynard
|
2013-10-07 10:04
|
|
Closing resolved issues that have not been updated in more than 4 months. |
|