public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "ro at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug target/61079] New: #pragma fini doesn't apply without definition
Date: Tue, 06 May 2014 13:48:00 -0000	[thread overview]
Message-ID: <bug-61079-4@http.gcc.gnu.org/bugzilla/> (raw)

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

            Bug ID: 61079
           Summary: #pragma fini doesn't apply without definition
           Product: gcc
           Version: 4.9.0
            Status: UNCONFIRMED
          Severity: normal
          Priority: P3
         Component: target
          Assignee: unassigned at gcc dot gnu.org
          Reporter: ro at gcc dot gnu.org
              Host: *-*-solaris2.*
            Target: *-*-solaris2.*
             Build: *-*-solaris2.*

Consider the following testcase:

$ cat dtor-pragma-decl.c   
#pragma fini(dtor)
void dtor (void);
$ gcc -S dtor-pragma-decl.c 
$ cat dtor-pragma-decl.s
        .file   "dtor-pragma-decl.c"
        .ident  "GCC: (GNU) 4.9.0"
$ cc -S dtor-pragma-decl.c
$ cat dtor-pragma-decl.s
[...]
        .file   "dtor-pragma-decl.c"
        .section        .fini,"ax"
        call    dtor
        nop

I.e. Studio cc calls dtor from a .fini section, while gcc ignores the pragma.

I'm seeing the same behavior with __attribute__((destructor)), which newer
versions of Studio cc understand.

At least for the pragma case, which gcc implements for Studio compatiblity,
this
seems wrong.

  Rainer


             reply	other threads:[~2014-05-06 13:48 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-05-06 13:48 ro at gcc dot gnu.org [this message]
2014-05-06 13:49 ` [Bug target/61079] " ro at gcc dot gnu.org
2015-04-22 12:00 ` jakub at gcc dot gnu.org
2015-07-16  9:17 ` rguenth 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-61079-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).