public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "dominiq at lps dot ens.fr" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug fortran/49565] character(kind=4) is emitted as DW_ATE_unsigned, not DW_ATE_unsigned_char
Date: Tue, 20 Oct 2015 21:54:00 -0000	[thread overview]
Message-ID: <bug-49565-4-ZE6jM0SxiD@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-49565-4@http.gcc.gnu.org/bugzilla/>

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=49565

Dominique d'Humieres <dominiq at lps dot ens.fr> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
             Status|UNCONFIRMED                 |WAITING
   Last reconfirmed|                            |2015-10-20
                 CC|                            |jakub at gcc dot gnu.org
     Ever confirmed|0                           |1

--- Comment #6 from Dominique d'Humieres <dominiq at lps dot ens.fr> ---
> Now moved to http://www.dwarfstd.org/ShowIssue.php?issue=121221.1&type=closed
>
> Note: It is listed under "resolved issues".

Any progress after two years and a half?


  parent reply	other threads:[~2015-10-20 21:54 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-06-28 15:55 [Bug fortran/49565] New: " tromey at gcc dot gnu.org
2011-06-28 16:08 ` [Bug fortran/49565] " burnus at gcc dot gnu.org
2011-06-28 16:45 ` burnus at gcc dot gnu.org
2011-06-28 16:55 ` burnus at gcc dot gnu.org
2012-04-16 22:04 ` burnus at gcc dot gnu.org
2013-03-15 17:50 ` burnus at gcc dot gnu.org
2015-10-20 21:54 ` dominiq at lps dot ens.fr [this message]
2024-03-20 21:54 ` anlauf at gcc dot gnu.org
2024-03-21  2:57 ` tromey at gcc dot gnu.org
2024-03-21 18:35 ` anlauf at gcc dot gnu.org

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=bug-49565-4-ZE6jM0SxiD@http.gcc.gnu.org/bugzilla/ \
    --to=gcc-bugzilla@gcc.gnu.org \
    --cc=gcc-bugs@gcc.gnu.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body. 
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).