public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "howarth at nitro dot med dot uc dot edu" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug middle-end/38868] r143152 breaks output routines in xplor-nih
Date: Sat, 17 Jan 2009 01:17:00 -0000 [thread overview]
Message-ID: <20090117011731.17282.qmail@sourceware.org> (raw)
In-Reply-To: <bug-38868-11113@http.gcc.gnu.org/bugzilla/>
------- Comment #17 from howarth at nitro dot med dot uc dot edu 2009-01-17 01:17 -------
Hmm, I can't look at what happens to START or STOP at those break points
because gdb reports...
Breakpoint 1, print2 (qspcl=.TRUE., renrl=()) at print2.f:81
81 WRITE(LINE(START:STOP),'(4A)') ' E(',ANER(J),')=',ST(1:STLEN)
(gdb) p START
$1 = <variable optimized away by compiler>
Current language: auto; currently fortran
--
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=38868
next prev parent reply other threads:[~2009-01-17 1:17 UTC|newest]
Thread overview: 52+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-01-16 7:07 [Bug middle-end/38868] New: " howarth at nitro dot med dot uc dot edu
2009-01-16 7:07 ` [Bug middle-end/38868] " howarth at nitro dot med dot uc dot edu
2009-01-16 7:08 ` howarth at nitro dot med dot uc dot edu
2009-01-16 7:10 ` howarth at nitro dot med dot uc dot edu
2009-01-16 7:11 ` howarth at nitro dot med dot uc dot edu
2009-01-16 7:12 ` howarth at nitro dot med dot uc dot edu
2009-01-16 7:14 ` howarth at nitro dot med dot uc dot edu
2009-01-16 7:21 ` howarth at nitro dot med dot uc dot edu
2009-01-16 8:14 ` howarth at nitro dot med dot uc dot edu
2009-01-16 9:42 ` rguenth at gcc dot gnu dot org
2009-01-16 10:00 ` dominiq at lps dot ens dot fr
2009-01-16 15:27 ` howarth at nitro dot med dot uc dot edu
2009-01-16 15:34 ` howarth at nitro dot med dot uc dot edu
2009-01-17 0:50 ` howarth at nitro dot med dot uc dot edu
2009-01-17 0:58 ` howarth at nitro dot med dot uc dot edu
2009-01-17 1:03 ` howarth at nitro dot med dot uc dot edu
2009-01-17 1:14 ` howarth at nitro dot med dot uc dot edu
2009-01-17 1:17 ` howarth at nitro dot med dot uc dot edu [this message]
2009-01-17 10:57 ` rguenth at gcc dot gnu dot org
2009-01-17 12:29 ` dominiq at lps dot ens dot fr
2009-01-17 12:54 ` jvdelisle at gcc dot gnu dot org
2009-01-17 15:11 ` sebpop at gmail dot com
2009-01-17 16:40 ` jvdelisle at gcc dot gnu dot org
2009-01-17 22:51 ` [Bug middle-end/38868] [4.4 Regression] " burnus at gcc dot gnu dot org
2009-01-17 23:23 ` howarth at nitro dot med dot uc dot edu
2009-01-17 23:28 ` dominiq at lps dot ens dot fr
2009-01-17 23:48 ` dominiq at lps dot ens dot fr
2009-01-18 12:01 ` dominiq at lps dot ens dot fr
2009-01-18 12:06 ` dominiq at lps dot ens dot fr
2009-01-18 12:50 ` dominiq at lps dot ens dot fr
2009-01-18 13:13 ` dominiq at lps dot ens dot fr
2009-01-18 13:24 ` burnus at gcc dot gnu dot org
2009-01-18 13:25 ` burnus at gcc dot gnu dot org
2009-01-18 17:02 ` howarth at nitro dot med dot uc dot edu
2009-01-18 19:49 ` howarth at nitro dot med dot uc dot edu
2009-01-19 10:30 ` rguenth at gcc dot gnu dot org
2009-01-19 10:33 ` bonzini at gnu dot org
2009-01-19 10:36 ` bonzini at gnu dot org
2009-01-19 10:51 ` rguenth at gcc dot gnu dot org
2009-01-19 11:04 ` bonzini at gnu dot org
2009-01-19 12:20 ` rguenth at gcc dot gnu dot org
2009-01-19 12:37 ` rguenth at gcc dot gnu dot org
2009-01-19 12:40 ` [Bug target/38868] " rguenth at gcc dot gnu dot org
2009-01-19 12:41 ` rguenth at gcc dot gnu dot org
2009-01-19 14:06 ` bonzini at gnu dot org
2009-01-19 15:04 ` bonzini at gnu dot org
2009-01-19 19:32 ` dominiq at lps dot ens dot fr
2009-01-19 23:44 ` howarth at nitro dot med dot uc dot edu
2009-01-20 13:24 ` bonzini at gcc dot gnu dot org
2009-01-20 13:25 ` bonzini at gnu dot org
2009-01-20 14:27 ` hjl dot tools at gmail dot com
2009-01-24 15:26 ` hjl 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=20090117011731.17282.qmail@sourceware.org \
--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).