rebase

@jansvoboda11 Actually, we could give you access to an AIX machine to debug this. Would that work for you?

@jansvoboda11 Thanks for taking care of the other tests. I'm not sure how this could be reproduced not on AIX. I'll have to investigate.

Added a comment and rebase

Restore patch (lost part of the patch when rebasing)

rebase

It looks like this PR isn't configured right to run the libc++ CI

rebase

Sorry for the late response @jansvoboda11, when lookupModuleFile is called, the file build/tools/clang/test/Index/Core/Output/index-with-module.m.tmp.mcp/A03A61VI43WA/ModA-21USRMHJNU3PG.pcm doesn't exist. So it seems there's some issue with the creation of the file.

Get full AIX version

LGTM, thanks

Thanks for the reviews. Just made some small changes:

• Changed the write order of the info section to match XCOFF convention
• Use advanceFileOffset now that it has landed

rerun CI

-Return the new RawPointer
-Added a TODO

Update patch

Update patch

Addressed comments

Remove old comment

Fix endianness of the padding.

Remove whitespace

Address comments

Hi, the following assertion is getting tripped on AIX:

Thanks @ldionne

Rerun CI

Fix formatting

Updated to use both a newline and null byte to separate command lines.

Thanks for the review @stephenpeckham, I updated the patch with the requested changes.

Fix formatting

Thanks for the review @scott.linder. I applied the changes you requested with some differences.

I'm not sure if it's this commit or one of the other llvm-exegesis commits you pushed, but there's a build failure on AIX now:

/scratch/powerllvm/powerllvm_env/aix-ppc64/clang-ppc64-aix/llvm-project/llvm/tools/llvm-exegesis/lib/X86/Target.cpp:49:33: error: unused variable 'VAddressSpaceCeiling' [-Werror,-Wunused-const-variable]
static constexpr const intptr_t VAddressSpaceCeiling = 0x0000800000000000;

https://lab.llvm.org/buildbot/#/builders/214/builds/8173/steps/5/logs/stdio

@sepavloff Thanks, that should address it

The test LLVM :: tools/llvm-symbolizer/input-file-err.test fails because it expects "Is a directory" as an error message, but we currently get "The file was not recognized as a valid object file" on AIX.
https://lab.llvm.org/buildbot/#/builders/214/builds/8134/steps/6/logs/FAIL__LLVM__input-file-err_test

Hi, on AIX we're getting the error: "The file was not recognized as a valid object file instead of the expected error"

Hi, there's a test failure on AIX, could you take a look please?

This caused a failure on AIX
https://lab.llvm.org/buildbot/#/builders/214/builds/7990/steps/6/logs/FAIL__lit___use-llvm-tool_py

Ping

In D119441#4340630, @Mordante wrote:

I see several comments off @ldionne and @hubert.reinterpretcast not marked as done. Are they done?

Hi, this fails on AIX. It looks like it still produces the /tmp/lit-tmp-*/[ab]-*.json format. Can you take a look please?

• Trigger CI

Ping

• Trigger CI

• Trigger CI

My mistake, I confirmed locally that it's D149173. Thanks

It looks like this caused a failure on AIX, could you take a look please?

• Trigger CI

Since I don't have access to a system with a 16-bit wchar_t it would be great if you could look at fixing the tests too.