public inbox for linux-ia64@vger.kernel.org
 help / color / mirror / Atom feed
From: David Mosberger <davidm@napali.hpl.hp.com>
To: linux-ia64@vger.kernel.org
Subject: Re: [Linux-ia64] segv with gas using gcc 3.2
Date: Wed, 29 Jan 2003 17:12:05 +0000	[thread overview]
Message-ID: <marc-linux-ia64-105590709805769@msgid-missing> (raw)
In-Reply-To: <marc-linux-ia64-105590709805767@msgid-missing>

>>>>> On Wed, 29 Jan 2003 09:21:09 -0600, Robert K Gjertsen <gjertsen@us.ibm.com> said:

  Rob> I'm seeing gas yak/segv on some assembly code that we use to
  Rob> avoid pulling extraneous instructions into the instruction
  Rob> cache (avoid debugging code when debugging is turned off).
  Rob> This used to work with gcc 2.96 but now dies with gcc 3.2 when
  Rob> optimizations are turned on (-O or higher). I'm trying to
  Rob> reduce this to a smaller and manageable case and also figure
  Rob> out whether I'm doing something ill-advised given that we are
  Rob> making some assumptions on how the code is ordered in the
  Rob> remote section (works OK on i386 with gcc 3.2).  Just seeing if
  Rob> someone may have some insight on my example below.

Perhaps the block-reordering is causing the problems for you?
Might want to try -fno-reorder-blocks.

A general comment: I'd highly discourage to switch sections within a
procedure.  The problem is that the unwind info will be all wrong
otherwise.

	--david


  reply	other threads:[~2003-01-29 17:12 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-01-29 15:21 [Linux-ia64] segv with gas using gcc 3.2 Robert K Gjertsen
2003-01-29 17:12 ` David Mosberger [this message]
2003-01-30 16:08 ` Jim Wilson

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=marc-linux-ia64-105590709805769@msgid-missing \
    --to=davidm@napali.hpl.hp.com \
    --cc=linux-ia64@vger.kernel.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