public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "dcb314 at hotmail dot com" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug lto/98912] New: valgrind error in default_elf_asm_output_ascii
Date: Mon, 01 Feb 2021 10:44:35 +0000	[thread overview]
Message-ID: <bug-98912-4@http.gcc.gnu.org/bugzilla/> (raw)

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

            Bug ID: 98912
           Summary: valgrind error in default_elf_asm_output_ascii
           Product: gcc
           Version: unknown
            Status: UNCONFIRMED
          Severity: normal
          Priority: P3
         Component: lto
          Assignee: unassigned at gcc dot gnu.org
          Reporter: dcb314 at hotmail dot com
                CC: marxin at gcc dot gnu.org
  Target Milestone: ---

Created attachment 50105
  --> https://gcc.gnu.org/bugzilla/attachment.cgi?id=50105&action=edit
fortran source code

For the attached fortran source code file, compiled as follows:

$ /home/dcb/gcc/results.20210131.valgrind/bin/gfortran -flto=auto getfname.f

does this:

==29891== Conditional jump or move depends on uninitialised value(s)
==29891==    at 0xF68B43: default_elf_asm_output_ascii(_IO_FILE*, char const*,
u
nsigned int) (varasm.c:8285)
==29891==    by 0xF68A8F: assemble_string(char const*, int) (varasm.c:2069)
==29891==    by 0xAAA5EF: lhd_append_data(void const*, unsigned long, void*)
(la
nghooks.c:823)
==29891==    by 0xAFC984: produce_lto_section (lto-streamer-out.c:2675)

             reply	other threads:[~2021-02-01 10:44 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-02-01 10:44 dcb314 at hotmail dot com [this message]
2021-02-01 14:47 ` [Bug lto/98912] " marxin at gcc dot gnu.org
2021-02-01 14:52 ` jakub at gcc dot gnu.org
2021-02-01 14:58 ` dcb314 at hotmail dot com
2021-02-02  9:25 ` marxin at gcc dot gnu.org
2021-02-02  9:31 ` jakub at gcc dot gnu.org
2021-02-03  9:54 ` marxin at gcc dot gnu.org
2021-02-03 12:19 ` cvs-commit at gcc dot gnu.org
2021-02-03 12:19 ` marxin 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-98912-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: 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).