public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "aldot at gcc dot gnu dot org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c/35034] assembler errors when building gcc/unwind-*.c at -O0 or -O1
Date: Thu, 31 Jan 2008 15:10:00 -0000	[thread overview]
Message-ID: <20080131144744.16189.qmail@sourceware.org> (raw)
In-Reply-To: <bug-35034-11811@http.gcc.gnu.org/bugzilla/>



------- Comment #4 from aldot at gcc dot gnu dot org  2008-01-31 14:47 -------
Smaller testcase:
-----------------------------------
$ cat pr35034-1.c
/* PR 35034 - fails to mangle function names for different TUs.  */
/* { dg-do compile } */
/* { dg-options "-combine -O0" } */
/* { dg-additional-sources pr35034-2.c } */
typedef int int_t;

static void
size_of_encoded_value (void)
{
};
extern int pthread_once (int_t *__once_control,
    void (*__init_routine) (void));
static __typeof(pthread_once) __gthrw_pthread_once __attribute__
((__weakref__("pthread_once")));

-----------------------------------
$ cat pr35034-2.c 
void size_of_encoded_value (void)
{
};
-----------------------------------


Gives with current trunk:
$ gcc-4.3-HEAD pr35034-1.c pr35034-2.c -O0 -c -o foo.o -combine -pipe
{standard input}: Assembler messages:
{standard input}:12: Error: symbol `size_of_encoded_value' is already defined
$ gcc-4.3-HEAD pr35034-1.c pr35034-2.c -O0 -S -o - -combine -pipe
        .file   "pr35034-1.c"
        .text
        .type   size_of_encoded_value, @function
size_of_encoded_value:
        pushl   %ebp
        movl    %esp, %ebp
        popl    %ebp
        ret
        .size   size_of_encoded_value, .-size_of_encoded_value
.globl size_of_encoded_value
        .type   size_of_encoded_value, @function
size_of_encoded_value:
        pushl   %ebp
        movl    %esp, %ebp
        popl    %ebp
        ret
        .size   size_of_encoded_value, .-size_of_encoded_value
        .weakref        __gthrw_pthread_once,pthread_once
        .ident  "GCC: (GNU) 4.3.0 20080131 (experimental)"
        .section        .note.GNU-stack,"",@progbits


-- 

aldot at gcc dot gnu dot org changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
           Keywords|                            |build, wrong-code
      Known to fail|                            |4.3.0


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


  parent reply	other threads:[~2008-01-31 14:48 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-01-30 22:19 [Bug c/35034] New: assembler errors when building gcc/unwind-*.c aldot at gcc dot gnu dot org
2008-01-30 23:16 ` [Bug c/35034] assembler errors when building gcc/unwind-*.c at -O0 or -O1 aldot at gcc dot gnu dot org
2008-01-31 10:40 ` rguenth at gcc dot gnu dot org
2008-01-31 12:22 ` jakub at gcc dot gnu dot org
2008-01-31 15:10 ` aldot at gcc dot gnu dot org [this message]
2008-01-31 15:12 ` [Bug c/35034] [4.3 Regression] " aldot at gcc dot gnu dot org
2008-01-31 15:19 ` [Bug c/35034] assembler errors when building gcc/unwind-*.c at -O0 or -O1 with IMA rguenth at gcc dot gnu dot org
2008-01-31 15:19 ` rguenth at gcc dot gnu dot org
2008-01-31 15:20 ` aldot at gcc dot gnu dot org
2008-01-31 15:55 ` aldot at gcc dot gnu dot org
2008-01-31 15:59 ` rguenth at gcc dot gnu dot org
2008-12-29 14:28 ` [Bug c/35034] weakref vs. -combine pinskia at gcc dot gnu dot org
2010-09-17  9:08 ` 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=20080131144744.16189.qmail@sourceware.org \
    --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).