Re: [RFC PATCH] Emit DW_LANG_Fortran{03,08}

2015-02-09 Thread Mark Wielaard
On Wed, 2015-02-04 at 23:19 +0100, Jakub Jelinek wrote: > On Wed, Feb 04, 2015@01:58:32PM -0800, Cary Coutant wrote: > > > DW_LANG_Fortran03 and DW_LANG_Fortran08 DW_AT_language values were > > > recently > > > accepted into DWARF5. This patch changes GCC to handle those similarly to > > > how e.

Re: [RFC PATCH] Emit DW_LANG_Fortran{03,08}

2015-02-04 Thread Cary Coutant
>> did with -gdwarf-4). We're still putting a version number of 2 in the >> compilation unit header! But I guess even upgrading the CU header to > > We are not. On most targets we default to -gdwarf-4 and emit v. 4: Oops, sorry, you're right. I carelessly misread this: dw2_asm_output_data (2,

Re: [RFC PATCH] Emit DW_LANG_Fortran{03,08}

2015-02-04 Thread Jakub Jelinek
On Wed, Feb 04, 2015 at 01:58:32PM -0800, Cary Coutant wrote: > > DW_LANG_Fortran03 and DW_LANG_Fortran08 DW_AT_language values were recently > > accepted into DWARF5. This patch changes GCC to handle those similarly to > > how e.g. the -std=c++11, -std=c++14 or -std=c11 are handled. > > > > As it

Re: [RFC PATCH] Emit DW_LANG_Fortran{03,08}

2015-02-04 Thread Cary Coutant
> PS: Talking about DWARF5, do you know when it will be available as public > draft? I am especially looking forward to > http://dwarfstd.org/ShowIssue.php?issue=121221.1 (Allow DW_AT_type with > DW_TAG_string_type), which would be a low-hanging fruit in terms of > implementation. Contrary to the a

Re: [RFC PATCH] Emit DW_LANG_Fortran{03,08}

2015-02-04 Thread Cary Coutant
> DW_LANG_Fortran03 and DW_LANG_Fortran08 DW_AT_language values were recently > accepted into DWARF5. This patch changes GCC to handle those similarly to > how e.g. the -std=c++11, -std=c++14 or -std=c11 are handled. > > As it will take some time for consumers to catch up, I'm enabling that > only

Re: [RFC PATCH] Emit DW_LANG_Fortran{03,08}

2015-01-27 Thread Tobias Burnus
Jakub Jelinek wrote: DW_LANG_Fortran03 and DW_LANG_Fortran08 DW_AT_language values were recently accepted into DWARF5. This patch changes GCC to handle those similarly to how e.g. the -std=c++11, -std=c++14 or -std=c11 are handled. For completeness: gfortran currently produces "GNU Fortran" an

Re: [RFC PATCH] Emit DW_LANG_Fortran{03,08}

2015-01-27 Thread Jakub Jelinek
On Tue, Jan 27, 2015 at 01:52:12PM -0500, David Malcolm wrote: > > @@ -398,6 +399,11 @@ gfc_post_options (const char **pfilename > > > >gfc_cpp_post_options (); > > > > + if (gfc_option.allow_std & GFC_STD_F2008) > > +lang_hooks.name = "GNU Fortran2008"; > > + else if (gfc_option.allo

Re: [RFC PATCH] Emit DW_LANG_Fortran{03,08}

2015-01-27 Thread David Malcolm
On Tue, 2015-01-27 at 19:19 +0100, Jakub Jelinek wrote: > Hi! > > DW_LANG_Fortran03 and DW_LANG_Fortran08 DW_AT_language values were recently > accepted into DWARF5. This patch changes GCC to handle those similarly to > how e.g. the -std=c++11, -std=c++14 or -std=c11 are handled. > > As it will

[RFC PATCH] Emit DW_LANG_Fortran{03,08}

2015-01-27 Thread Jakub Jelinek
Hi! DW_LANG_Fortran03 and DW_LANG_Fortran08 DW_AT_language values were recently accepted into DWARF5. This patch changes GCC to handle those similarly to how e.g. the -std=c++11, -std=c++14 or -std=c11 are handled. As it will take some time for consumers to catch up, I'm enabling that only if -g