public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "bangerth at dealii dot org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c++/11376] [3.3/3.4 regression] mozilla-1.4 miscompiled
Date: Tue, 08 Jul 2003 01:21:00 -0000	[thread overview]
Message-ID: <20030708012103.15046.qmail@sources.redhat.com> (raw)
In-Reply-To: <20030630081619.11376.sirl@gcc.gnu.org>

PLEASE REPLY TO gcc-bugzilla@gcc.gnu.org ONLY, *NOT* gcc-bugs@gcc.gnu.org.

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



------- Additional Comments From bangerth at dealii dot org  2003-07-08 01:21 -------
As Andrew said, inlining might be different (functions defined in-class
have an implicit "inline" attribute, which is not the case if a function
is defined out-of-class). You may see whether you can trigger the abort
in the out-of-class case when you pass -finline-functions to gcc, which
makes all functions eligible for inlining. Alternatively, use -O3, which
implies -finline-functions.

As a hint for further testcase reduction: make all classes structs, and
remove the public/private/protected markers. Then try to do some of
the inlining by hand, by replacing the use of accessor functions by
direct accesses of the respective values, and subsequent removal of
the accessor functions. By looking at the code, it's obvious that you are
very close to the hailed one-page-limit, at which everything suddenly
becomes clear. (I'd like to help here, but can't for lack of a respective
platform...)

W.


  parent reply	other threads:[~2003-07-08  1:21 UTC|newest]

Thread overview: 44+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-06-30  8:16 [Bug c++/11376] New: " sirl at gcc dot gnu dot org
2003-06-30  8:19 ` [Bug c++/11376] " sirl at gcc dot gnu dot org
2003-06-30  8:20 ` sirl at gcc dot gnu dot org
2003-06-30  8:25 ` sirl at gcc dot gnu dot org
2003-06-30 13:20 ` giovannibajo at libero dot it
2003-06-30 13:40 ` kevin dot hendricks at sympatico dot ca
2003-06-30 13:54 ` kevin dot hendricks at sympatico dot ca
2003-06-30 14:04 ` kevin dot hendricks at sympatico dot ca
2003-06-30 14:35 ` kevin dot hendricks at sympatico dot ca
2003-07-02  2:08 ` mmitchel at gcc dot gnu dot org
2003-07-02  5:41 ` franz dot sirl-kernel at lauterbach dot com
2003-07-07 15:46 ` giovannibajo at libero dot it
2003-07-07 16:11 ` kevin dot hendricks at sympatico dot ca
2003-07-08  0:14 ` kevin dot hendricks at sympatico dot ca
2003-07-08  0:22 ` pinskia at physics dot uc dot edu
2003-07-08  0:59 ` kevin dot hendricks at sympatico dot ca
2003-07-08  1:21 ` bangerth at dealii dot org [this message]
2003-07-08  2:05 ` kevin dot hendricks at sympatico dot ca
2003-07-08  2:33 ` kevin dot hendricks at sympatico dot ca
2003-07-08  5:36 ` mark at codesourcery dot com
2003-07-08 16:32 ` janis187 at us dot ibm dot com
2003-07-08 17:18 ` dberlin at gcc dot gnu dot org
2003-07-08 17:34 ` kevin dot hendricks at sympatico dot ca
2003-07-08 17:50 ` sirl at gcc dot gnu dot org
2003-07-08 18:29 ` kevin dot hendricks at sympatico dot ca
2003-07-08 19:07 ` kevin dot hendricks at sympatico dot ca
2003-07-08 19:13 ` sirl at gcc dot gnu dot org
2003-07-08 19:19 ` mark at codesourcery dot com
2003-07-08 19:35 ` bangerth at dealii dot org
2003-07-08 19:42 ` sirl at gcc dot gnu dot org
2003-07-08 19:50 ` kevin dot hendricks at sympatico dot ca
2003-07-08 19:59 ` pinskia at physics dot uc dot edu
2003-07-08 20:02 ` kevin dot hendricks at sympatico dot ca
2003-07-08 20:10 ` bangerth at dealii dot org
2003-07-08 21:25 ` sirl at gcc dot gnu dot org
2003-07-08 21:57 ` bangerth at dealii dot org
2003-07-08 22:00 ` dbaron at dbaron dot org
2003-07-08 23:26 ` dbaron at dbaron dot org
2003-07-08 23:55 ` bangerth at dealii dot org
2003-07-09 16:20 ` scc at mozilla dot org
2003-08-08  8:29 ` gbeauchesne at mandrakesoft dot com
2005-05-07 22:30 ` pinskia at gcc dot gnu dot org
2005-06-05  9:16 ` pinskia at gcc dot gnu dot org
2005-06-05  9:17 ` pinskia 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=20030708012103.15046.qmail@sources.redhat.com \
    --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).