public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "zuxy dot meng at gmail dot com" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c/35661]  New: __attribute__((cold)) generates wrong code
Date: Fri, 21 Mar 2008 20:15:00 -0000	[thread overview]
Message-ID: <bug-35661-12845@http.gcc.gnu.org/bugzilla/> (raw)

On MinGW32, GCC 4.3.0 marks the .text.unlikely section as "w"(writable) instead
of "x"(executable), which makes the assembler to pad the section with zeros
instead of NOPs. Runtime behavior is almost always incorrect and in many cases
an application will crash.


-- 
           Summary: __attribute__((cold)) generates wrong code
           Product: gcc
           Version: 4.3.0
            Status: UNCONFIRMED
          Severity: major
          Priority: P3
         Component: c
        AssignedTo: unassigned at gcc dot gnu dot org
        ReportedBy: zuxy dot meng at gmail dot com
 GCC build triplet: i686-pc-mingw32
  GCC host triplet: i686-pc-mingw32
GCC target triplet: i686-pc-mingw32


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


             reply	other threads:[~2008-03-21 20:15 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-03-21 20:15 zuxy dot meng at gmail dot com [this message]
2008-03-21 20:18 ` [Bug target/35661] " pinskia at gcc dot gnu dot org
2008-03-21 20:19 ` zuxy dot meng at gmail dot com
2008-03-21 20:21 ` zuxy dot meng at gmail dot com
2008-03-21 20:22 ` pinskia at gcc dot gnu dot org
2008-03-21 20:24 ` zuxy dot meng at gmail dot com
2008-04-07  2:01 ` pinskia at gcc dot gnu dot org
2008-04-07  6:01 ` zuxy dot meng at gmail dot com
2008-04-13 12:19 ` zuxy dot meng at gmail dot com
2008-04-14 23:49 ` dannysmith at gcc dot gnu dot org
2008-05-11 21:04 ` dannysmith at gcc dot gnu dot org
2008-05-11 21:10 ` dannysmith at users dot sourceforge dot net

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-35661-12845@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).