public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "tromey at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug fortran/49565] New: character(kind=4) is emitted as DW_ATE_unsigned, not DW_ATE_unsigned_char Date: Tue, 28 Jun 2011 15:55:00 -0000 [thread overview] Message-ID: <bug-49565-4@http.gcc.gnu.org/bugzilla/> (raw) http://gcc.gnu.org/bugzilla/show_bug.cgi?id=49565 Summary: character(kind=4) is emitted as DW_ATE_unsigned, not DW_ATE_unsigned_char Product: gcc Version: unknown Status: UNCONFIRMED Severity: normal Priority: P3 Component: fortran AssignedTo: unassigned@gcc.gnu.org ReportedBy: tromey@gcc.gnu.org I compiled this program with svn trunk gfortran. I used -gdwarf-4 -g. character(kind=4) :: c character(kind=4,len=5) :: str c = 4_'\u00AE' str = 4_'\u00AE\u01DD' open(6,encoding='utf-8') print *, c print *, str end Then I examined the DWARF. 'c' is ultimately of type: <1><cf>: Abbrev Number: 7 (DW_TAG_base_type) <d0> DW_AT_byte_size : 4 <d1> DW_AT_encoding : 7 (unsigned) <d2> DW_AT_name : (indirect string, offset: 0x67): character(kind=4) I think the encoding should be DW_ATE_unsigned_char instead.
next reply other threads:[~2011-06-28 15:55 UTC|newest] Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top 2011-06-28 15:55 tromey at gcc dot gnu.org [this message] 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 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@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: linkBe 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).