public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "neroden at gcc dot gnu dot org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug optimization/11386] GNU Emacs 21.3 failed to install using GCC 3.3, but GCC 3.2.3 works.
Date: Wed, 09 Jul 2003 02:19:00 -0000	[thread overview]
Message-ID: <20030709021949.9366.qmail@sources.redhat.com> (raw)
In-Reply-To: <20030630221211.11386.ishikawa@yk.rim.or.jp>

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

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



------- Additional Comments From neroden at gcc dot gnu dot org  2003-07-09 02:19 -------
> Probably I should be able to find a difference between
>   temacs (by GCC 3.2.3) objdump segment listing and
>   temacs (by GCC 3.3)   objdump segment listing.
>
>   bootstrap-emacs (by GCC 3.2.3), and
>   bootstrap-emacs (by GCC 3.3).

See if you can find a difference in the section order, segment order, symbol table, or some such, which might trigger lurking unexec bugs.  
Differences in the actual machine code or the length thereof are not going to be meaningful due to the number of changes in code generation. :-P

Looking at unexelf.c, I really want this to be a bug in it, because it's an evil file. :-)


  parent reply	other threads:[~2003-07-09  2:19 UTC|newest]

Thread overview: 30+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-06-30 22:12 [Bug c/11386] New: " ishikawa at yk dot rim dot or dot jp
2003-07-01  9:46 ` [Bug c/11386] " ebotcazou at gcc dot gnu dot org
2003-07-01  9:54 ` [Bug optimization/11386] " ebotcazou at gcc dot gnu dot org
2003-07-02  9:43 ` ishikawa at yk dot rim dot or dot jp
2003-07-03 16:57 ` simon dot marshall at misys dot com
2003-07-03 18:18 ` ishikawa at yk dot rim dot or dot jp
2003-07-03 19:20 ` ebotcazou at libertysurf dot fr
2003-07-04 17:11 ` ebotcazou at gcc dot gnu dot org
2003-07-04 20:59 ` ishikawa at yk dot rim dot or dot jp
2003-07-05 14:34   ` Christian Ehrhardt
2003-07-04 21:37 ` ebotcazou at libertysurf dot fr
2003-07-05 14:35 ` ehrhardt at mathematik dot uni-ulm dot de
2003-07-07  1:47 ` ishikawa at yk dot rim dot or dot jp
2003-07-07  9:30 ` simon dot marshall at misys dot com
2003-07-07 10:23 ` ebotcazou at gcc dot gnu dot org
2003-07-07 23:25 ` ishikawa at yk dot rim dot or dot jp
2003-07-08  6:43 ` ebotcazou at libertysurf dot fr
2003-07-08 13:00 ` simon dot marshall at misys dot com
2003-07-09  0:12 ` neroden at gcc dot gnu dot org
2003-07-09  2:19 ` neroden at gcc dot gnu dot org [this message]
2003-07-09  8:17 ` simon dot marshall at misys dot com
2003-07-11  9:46 ` ishikawa at yk dot rim dot or dot jp
2003-07-11 10:09 ` simon dot marshall at misys dot com
2003-07-11 10:38 ` ebotcazou at gcc dot gnu dot org
2003-07-11 12:09 ` ebotcazou at gcc dot gnu dot org
2003-07-11 12:10 ` ebotcazou at gcc dot gnu dot org
2003-07-11 17:48 ` ebotcazou at gcc dot gnu dot org
2003-07-14 19:45 ` ebotcazou at gcc dot gnu dot org
2003-07-14 23:32 ` ishikawa at yk dot rim dot or dot jp
2003-07-15  1:31 ` bangerth at dealii 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=20030709021949.9366.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).