This is an archive of the discontinued LLVM Phabricator instance.

[NVPTX][tests] Do not run tests that require direct object generation
ClosedPublic

Authored by ikudrin on Mar 18 2022, 4:48 AM.

Details

Summary

NVPTX does not support generating binary files, which is required for these tests.

The majority of tests in 'DebugInfo/Generic' also require emitting object files, so they all are disabled for NVPTX.

Diff Detail

Event Timeline

ikudrin created this revision.Mar 18 2022, 4:48 AM
Herald added a project: Restricted Project. · View Herald TranscriptMar 18 2022, 4:48 AM
ikudrin requested review of this revision.Mar 18 2022, 4:48 AM
ikudrin added a subscriber: jholewinski.
ikudrin retitled this revision from [nvptx][tests] Do not run tests that require direct object generation to [NVPTX][tests] Do not run tests that require direct object generation.Mar 18 2022, 4:52 AM

The code LGTM. When object-emission was reintroduced in D98508, there was some discussion on whether XCore ought to use this feature, or provide an integrated assembler instead. Sorry I don't know NVPTX: is NVPTX different because it generates assembly as its natural output, and binary does not make sense? Or could it have an integrated assembler at some point?

The code LGTM. When object-emission was reintroduced in D98508, there was some discussion on whether XCore ought to use this feature, or provide an integrated assembler instead. Sorry I don't know NVPTX: is NVPTX different because it generates assembly as its natural output, and binary does not make sense? Or could it have an integrated assembler at some point?

As far as I know, there are no plans for adding the integrated assembler.

LGTM but I would prefer to hear from other reviewers who commented on object-emission before.

tra added a subscriber: tra.Mar 18 2022, 11:16 AM

The code LGTM. When object-emission was reintroduced in D98508, there was some discussion on whether XCore ought to use this feature, or provide an integrated assembler instead. Sorry I don't know NVPTX: is NVPTX different because it generates assembly as its natural output, and binary does not make sense? Or could it have an integrated assembler at some point?

NVPTX only generates assembly. It is not going to have native code generation any time soon. It it did, we'd have multiple native back-ends. In other words, LGTM as far as NVPTX back-end is concerned.

This revision was not accepted when it landed; it landed in state Needs Review.Mar 22 2022, 5:50 AM
This revision was landed with ongoing or failed builds.
This revision was automatically updated to reflect the committed changes.