On Wed, Apr 24, 2024 at 02:57:17PM -0700, Adrian Prantl wrote:
>
>
> > On Apr 24, 2024, at 2:49 PM, Jakub Jelinek wrote:
> >
> > On Wed, Apr 24, 2024 at 02:25:37PM -0700, Adrian Prantl via Dwarf-discuss
> > wrote:
> >> # C standard release dates for DW_AT_language_version, clarify semantics
>
> On Apr 24, 2024, at 2:49 PM, Jakub Jelinek wrote:
>
> On Wed, Apr 24, 2024 at 02:25:37PM -0700, Adrian Prantl via Dwarf-discuss
> wrote:
>> # C standard release dates for DW_AT_language_version, clarify semantics
>>
>> ## Background
>>
>> The list of languages at
On Wed, Apr 24, 2024 at 02:25:37PM -0700, Adrian Prantl via Dwarf-discuss wrote:
> # C standard release dates for DW_AT_language_version, clarify semantics
>
> ## Background
>
> The list of languages at https://dwarfstd.org/languages-v6.html does not list
> release dates for the ISO C standard.
The back story here is that I am trying to implement the new language
attributes in LLVM, which is why I'm finding all these bugs, omissions, and
ambiguities:
https://github.com/llvm/llvm-project/pull/89980
cheers,
Adrian
> On Apr 24, 2024, at 2:25 PM, Adrian Prantl via Dwarf-discuss
>
# Add versioning scheme for Fortran
## Background
The list of languages at https://dwarfstd.org/languages-v6.html does not list a
versioning scheme for Fortran, but we have DWARF 5 language constants for
FORTRAN77 through Fortran08.
## Proposed Changes
Augment the table of language encodings
# C standard release dates for DW_AT_language_version, clarify semantics
## Background
The list of languages at https://dwarfstd.org/languages-v6.html does not list
release dates for the ISO C standard. Producers need to know what version
numbers they should produce though. I scanned the ISO
Cary,
>DW_LANG_HIP/DW_LNAME_HIP was assigned first, but for some reason, the list
was out of order, so when I assigned >DW_LNAME_Assembly, it looked like
0x001c was the last code assigned. I think it would be safer to reassign
>DW_LNAME_Assembly as 0x0029.
I think it would be safer to just leave
Cary,
Actually, it would help my process if you would announce at each meeting
what language names and their corresponding issue numbers were processed in
the prior period. The point is to get that information into the Minutes. No
discussion needed, just an announcement. Actually if that
>
>
> It appears that DW_LNAME_HIP, proposed in 230120.4, never got
> incorporated into the DWARF working document (so there is no duplication).
> Perhaps because the Issue status is "Code Assigned" rather than Approved.
> That status really only applies to the V5 code assignment actually.
>
>
> It appears that DW_LNAME_HIP, proposed in 230120.4, never got
> incorporated into the DWARF working document (so there is no duplication).
> Perhaps because the Issue status is "Code Assigned" rather than Approved.
> That status really only applies to the V5 code assignment actually.
>
>
> On Apr 24, 2024, at 5:46 AM, Ron Brender wrote:
>
> It appears that DW_LNAME_HIP, proposed in 230120.4, never got incorporated
> into the DWARF working document (so there is no duplication). Perhaps because
> the Issue status is "Code Assigned" rather than Approved. That status really
>
It appears that DW_LNAME_HIP, proposed in 230120.4, never got incorporated
into the DWARF working document (so there is no duplication). Perhaps
because the Issue status is "Code Assigned" rather than Approved. That
status really only applies to the V5 code assignment actually.
Anyway, I'll fix
12 matches
Mail list logo
