This is the mail archive of the java-patches@gcc.gnu.org mailing list for the Java project.

Index Nav:	[Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav:	[Date Prev] [Date Next]	[Thread Prev] [Thread Next]
Other format:	[Raw text]

Re: Fix backtrace for interpreted code

From: Andrew Pinski <pinskia at physics dot uc dot edu>
To: Ranjit Mathew <rmathew at gmail dot com>
Cc: GCJ Patches <java-patches at gcc dot gnu dot org>, Andrew Haley <aph at redhat dot com>
Date: Thu, 14 Oct 2004 10:12:14 -0400
Subject: Re: Fix backtrace for interpreted code
References: <16749.27189.465623.731242@cuddles.cambridge.redhat.com> <416E2E60.2060409@gmail.com> <16750.23024.47167.731693@cuddles.cambridge.redhat.com> <39399b9d04101405563b7b34cb@mail.gmail.com> <16750.34034.269954.472181@cuddles.cambridge.redhat.com> <39399b9d04101407082f0c5db0@mail.gmail.com>

On Oct 14, 2004, at 10:08 AM, Ranjit Mathew wrote:

Always.  g++ always sets flag_unit_at_a_time, so functions are not
output in the order they're declared.


Oh! I didn't know that - thanks!
Would it be too gross?

Does not work, the basic blocks can be reordered too.

Thanks,
Andrew Pinski

Follow-Ups:
- Re: Fix backtrace for interpreted code
  - From: Andrew Haley

References:
- Fix backtrace for interpreted code
  - From: Andrew Haley
- Re: Fix backtrace for interpreted code
  - From: Ranjit Mathew
- Re: Fix backtrace for interpreted code
  - From: Andrew Haley
- Re: Fix backtrace for interpreted code
  - From: Ranjit Mathew
- Re: Fix backtrace for interpreted code
  - From: Andrew Haley
- Re: Fix backtrace for interpreted code
  - From: Ranjit Mathew

Index Nav:	[Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav:	[Date Prev] [Date Next]	[Thread Prev] [Thread Next]