Page MenuHomePhabricator

[AIX][CMake] Changes for building on AIX with XL and GCC

Authored by xingxue on Feb 14 2019, 1:13 PM.



In support of IBM's efforts to produce a viable C and C++ LLVM compiler for AIX (ref: RFC at, this patch adds customizations to the CMake files in order to properly invoke the host toolchain for the build on AIX. Additional changes to enable a successful build will follow.

Diff Detail


Event Timeline

xingxue created this revision.Feb 14 2019, 1:13 PM
sfertile added inline comments.Feb 15 2019, 8:55 AM
138 ↗(On Diff #186903)

I'm interested in why you choose bigtoc linker option over using large code model? From the little I understand about the bigtoc option it seems that large code model would be the preferable solution when expecting to have a toc that is a lot bigger then 64K.

138 ↗(On Diff #186903)

-fPIC is already specified. Even if the code is generated using the large code model, TOC overflow is a hard error for the linker unless if -bbigtoc is specified. On linking, the XL compiler specifies -bbigtoc to the linker in response -qpic=large.

You can see this for yourself if you compile the following with -q64 -qpic=large and link with only -q64:

#define x2A( BASE )  BASE ## a, BASE ## b
#define x2B( BASE )  x2A(BASE ## a), x2A(BASE ## b)
#define x2C( BASE )  x2B(BASE ## a), x2B(BASE ## b)
#define x2D( BASE )  x2C(BASE ## a), x2C(BASE ## b)
#define x2E( BASE )  x2D(BASE ## a), x2D(BASE ## b)
#define x2F( BASE )  x2E(BASE ## a), x2E(BASE ## b)
#define x2G( BASE )  x2F(BASE ## a), x2F(BASE ## b)
#define x2H( BASE )  x2G(BASE ## a), x2G(BASE ## b)
#define x2I( BASE )  x2H(BASE ## a), x2H(BASE ## b)
#define x2J( BASE )  x2I(BASE ## a), x2I(BASE ## b)
#define x2K( BASE )  x2J(BASE ## a), x2J(BASE ## b)

#define x2KA( BASE )  x2K(BASE ## a), x2K(BASE ## b)
#define x2KB( BASE )  x2KA(BASE ## a), x2KA(BASE ## b)
int x2KB( x );

int main(void) { x2KB( ++x ); }
138 ↗(On Diff #186903)

Okay, it seems -fPIC does not enable the large code model for GCC on AIX (but does for the new XL compilers). -mcmodel=large should be added for GCC; however, the linker option remains necessary.

chandlerc added inline comments.
37–41 ↗(On Diff #186903)

Is this correct though? I would expect non-hidden visibility checks to break things.

37–41 ↗(On Diff #186903)

My understanding is yes: AIX does not export by default. Maybe a comment in the code is warranted?

sfertile added inline comments.Feb 21 2019, 8:42 AM
138 ↗(On Diff #186903)

I had a look at the example. You are right, the code XL generates does need the link-option. The code generated for main uses the large code model with R_TOCU/R_TOCL relocations, but the compiler inserts a bunch of code that still uses small code model R_TOC relocations (namely ._start, ._thread_init, and ._C_runtime_startup). The code gcc generates for the example links just fine without the extra option as they only use large code model relocations. We need to add -mcmodel=large for gcc, and only use -bbigtoc for XL.

xingxue updated this revision to Diff 188459.Feb 26 2019, 2:13 PM

Address review comments:

  • Add comment regarding correctness of not applying a visibility attribute when using GCC on AIX.
  • Apply -mcmodel=large for GCC on AIX, and use -Wl,-bbigtoc for XL (on AIX) only.
xingxue marked 6 inline comments as done.Feb 26 2019, 2:16 PM
139 ↗(On Diff #188459)

For this and other instances of STREQUAL "XL", we should use MATCHES "XL" so that "XLClang" is also matched. See

hubert.reinterpretcast edited the summary of this revision. (Show Details)Feb 28 2019, 3:07 PM
xingxue updated this revision to Diff 188983.Mar 1 2019, 3:14 PM
xingxue marked an inline comment as done.

Address review comments:

  • Replaced 'STREQUAL "XL"' with 'MATCHES "XL"'.

I believe all comments on this have been addressed. This LGTM. I'll probably commit this on Monday.

This revision is now accepted and ready to land.Mar 1 2019, 4:31 PM
37 ↗(On Diff #188983)

__GNU__ is not the macro we want to check here (it checks for GNU Hurd, i.e., the OS). The intention is to check for GCC. I am not sure if there is a better way to check for "real" GCC as opposed to the GCC-compatible compilers other than to filter for each of the known compatible compilers that do not suffer from the same limitation as GCC.

xingxue updated this revision to Diff 190112.Mar 11 2019, 10:42 AM

Address review comments:

  • Check __GNUC__ for GCC instead of __GNU__ and exclude CLANG which also sets macro __GNUC__.
joerg added a subscriber: joerg.Mar 11 2019, 1:30 PM

Why do you exclude clang? I would expect LLVM at this point to not support visibility attributes on XCOFF either?

Why do you exclude clang? I would expect LLVM at this point to not support visibility attributes on XCOFF either?

The scope of this patch is to enable use of GCC and IBM XL compilers on AIX as build compilers for LLVM. The desired semantic of the line in question is to disable the use of the visibility attribute for GCC. The condition on __clang__ is meant to prevent gobbling up non-GCC compilers in the check for __GNUC__. The consideration of whether Clang should itself be exempted from the use of the visibility attribute on AIX seems premature.

This revision was automatically updated to reflect the committed changes.