public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "danglin at gcc dot gnu dot org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug lto/41597]  New: Bad .comm directive
Date: Mon, 05 Oct 2009 22:18:00 -0000	[thread overview]
Message-ID: <bug-41597-276@http.gcc.gnu.org/bugzilla/> (raw)

Executing on host: /test/gnu/gcc/objdir/gcc/xgcc -B/test/gnu/gcc/objdir/gcc/  
-
O2 -flto  -w -c  -o 20000105-1.o
/test/gnu/gcc/gcc/gcc/testsuite/gcc.c-torture/c
ompile/20000105-1.c    (timeout = 300)
/var/tmp//cc74uIsZ.s: Assembler messages:
/var/tmp//cc74uIsZ.s:105: Error: bad or irreducible absolute expression
/var/tmp//cc74uIsZ.s:105: Error: junk at end of line, first unrecognized
charact
er is `,'
compiler exited with status 1

The directive is:

        .comm   gnu_lto_v1,1,1

This apparently comes from here:

  /* Emit LTO marker if LTO info has been previously emitted.  This is
     used by collect2 to determine whether an object file contains IL.
     We used to emit an undefined reference here, but this produces
     link errors if an object file with IL is stored into a shared
     library without invoking lto1.  */
  if (flag_generate_lto)
    fprintf (asm_out_file,"\t.comm\tgnu_lto_v1,1,1\n");


-- 
           Summary: Bad .comm directive
           Product: gcc
           Version: 4.5.0
            Status: UNCONFIRMED
          Severity: normal
          Priority: P3
         Component: lto
        AssignedTo: unassigned at gcc dot gnu dot org
        ReportedBy: danglin at gcc dot gnu dot org
 GCC build triplet: hppa64-hp-hpux11.11
  GCC host triplet: hppa64-hp-hpux11.11
GCC target triplet: hppa64-hp-hpux11.11


http://gcc.gnu.org/bugzilla/show_bug.cgi?id=41597


             reply	other threads:[~2009-10-05 22:18 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-10-05 22:18 danglin at gcc dot gnu dot org [this message]
2009-10-06  0:11 ` [Bug lto/41597] " joseph at codesourcery dot com
2009-10-06 10:17 ` rguenth at gcc dot gnu dot org
2009-10-06 15:55 ` dave at hiauly1 dot hia dot nrc dot ca
2009-10-09 14:29 ` rguenth at gcc dot gnu dot org
2010-01-01 23:10 ` rguenth at gcc dot gnu dot org
2010-01-02 11:12 ` rguenth at gcc dot gnu dot org
2010-01-02 11:25 ` rguenth at gcc dot gnu dot 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-41597-276@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).