bug-binutils
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

[Bug gas/28447] New: [AIX] .file pseudo-op should accept multiple parame


From: dje at sourceware dot org
Subject: [Bug gas/28447] New: [AIX] .file pseudo-op should accept multiple parameters
Date: Tue, 12 Oct 2021 18:14:28 +0000

https://sourceware.org/bugzilla/show_bug.cgi?id=28447

            Bug ID: 28447
           Summary: [AIX] .file pseudo-op should accept multiple
                    parameters
           Product: binutils
           Version: 2.38 (HEAD)
            Status: NEW
          Severity: normal
          Priority: P2
         Component: gas
          Assignee: unassigned at sourceware dot org
          Reporter: dje at sourceware dot org
                CC: clement.chigot at atos dot net
  Target Milestone: ---
            Target: powerpc-ibm-aix*

On AIX, the .file pseudo-op is defined to accept multiple parameters.  The GNU
Assembler only accepts a single parameter.  GCC only emits one parameter, but
other compilers, such as Open XL/LLVM generate multiple parameters and elicit a
syntax error from GNU Assembler.

.file   "file.c","IBM Open XL C/C++ for AIX 17.1.0 (5725-C72, 5765-J18), LLVM
version 13.0.0git"

 .file StringConstant
 .file StringConstant, StringConstant1
 .file StringConstant,[StringConstant1], StringConstant2
 .file StringConstant,[StringConstant1],[StringConstant2], StringConstant3

The .file pseudo-op provides the symbol table information to the symbolic
debugger and the ld command. StringConstant is the file name, and it is used as
the name of an auxiliary symbol x_ftype == XTY_FN. If StringConstant1,
StringConstant2, and StringConstant3 are specified, these values are added to
the symbol table as the compiler time stamp with the x_ftype symbol set to
XTY_CT; compiler version with the x_ftype symbol set to XTY_CV; and
compiler-provided information with the x_ftype symbol set to XTY_CD.

-- 
You are receiving this mail because:
You are on the CC list for the bug.


reply via email to

[Prev in Thread] Current Thread [Next in Thread]