all messages for Emacs-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: David Reitter <david.reitter@gmail.com>
To: Dan Nicolaescu <dann@ics.uci.edu>
Cc: Ian Eure <ian@digg.com>, Emacs Development <emacs-devel@gnu.org>
Subject: Re: gcc 4.2 dump problems
Date: Thu, 6 Aug 2009 15:03:39 -0400	[thread overview]
Message-ID: <016ACD5B-B97C-4548-89C5-E1E6A581CC61@gmail.com> (raw)
In-Reply-To: <200908061824.n76IO3Wg012594@godzilla.ics.uci.edu>

[-- Attachment #1: Type: text/plain, Size: 811 bytes --]

On Aug 6, 2009, at 2:24 PM, Dan Nicolaescu wrote:
> I don't use gcc-4.2 anymore, but I've never seen such problems with it
> on GNU/Linux while using it.
>
> How did you determine that gcc-4.2 is the problem?

See Ian Eure's post to bug 3708 for this.  He installed GCC 4.2 on a  
10.5 machine and obtained similar results.
The error messages differ at times, but they do that on the 10.6  
machine that I tried it on, too.
(Building with 4.0 on 10.5 works fine.)

> Did you try different versions of gcc on the same machine, keeping the
> same version of binutils, and only gcc-4.2 had problems?

Ian, from your message, it looks like this is what you did, right?

> Have you tried compiling with -O0 ?  Did you also have problems when  
> using -O0 ?

Yes, I use -O0 routinely, including in the bug report.



[-- Attachment #2: smime.p7s --]
[-- Type: application/pkcs7-signature, Size: 2193 bytes --]

  reply	other threads:[~2009-08-06 19:03 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-08-06 17:25 gcc 4.2 dump problems David Reitter
2009-08-06 18:09 ` Werner LEMBERG
2009-08-06 18:24 ` Dan Nicolaescu
2009-08-06 19:03   ` David Reitter [this message]
2009-08-06 19:29     ` Dan Nicolaescu
2009-08-25 13:18     ` David Engster
2009-08-25 15:56       ` Ian Eure
2009-08-25 16:15         ` David Reitter
2009-08-26 13:32         ` David Engster

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=016ACD5B-B97C-4548-89C5-E1E6A581CC61@gmail.com \
    --to=david.reitter@gmail.com \
    --cc=dann@ics.uci.edu \
    --cc=emacs-devel@gnu.org \
    --cc=ian@digg.com \
    /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.
Code repositories for project(s) associated with this external index

	https://git.savannah.gnu.org/cgit/emacs.git
	https://git.savannah.gnu.org/cgit/emacs/org-mode.git

This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.