From: DJ Delorie <dj@redhat.com>
To: Richard Henderson <rth@redhat.com>
Cc: gcc-patches@gcc.gnu.org
Subject: Re: TPF: disable discriminators
Date: Tue, 31 Jul 2012 21:25:00 -0000 [thread overview]
Message-ID: <201207312109.q6VL9SCl027555@greed.delorie.com> (raw)
In-Reply-To: <501806B6.7020409@redhat.com> (message from Richard Henderson on Tue, 31 Jul 2012 09:24:22 -0700)
Ah, the original complaint was for a gcc branch which doesn't have
your strict-dwarf/discriminator patch.
How's this?
Index: gcc/config/s390/s390.c
===================================================================
--- gcc/config/s390/s390.c (revision 190017)
+++ gcc/config/s390/s390.c (working copy)
@@ -1651,12 +1651,21 @@ s390_option_override (void)
flag_prefetch_loop_arrays = 1;
/* Use the alternative scheduling-pressure algorithm by default. */
maybe_set_param_value (PARAM_SCHED_PRESSURE_ALGORITHM, 2,
global_options.x_param_values,
global_options_set.x_param_values);
+
+#ifdef TARGET_TPF
+ /* Don't emit DWARF3/4 unless specifically selected. The TPF
+ debuggers do not yet support DWARF 3/4. */
+ if (!global_options_set.x_dwarf_strict)
+ dwarf_strict = 1;
+ if (!global_options_set.x_dwarf_version)
+ dwarf_version = 2;
+#endif
}
/* Map for smallest class containing reg regno. */
const enum reg_class regclass_map[FIRST_PSEUDO_REGISTER] =
{ GENERAL_REGS, ADDR_REGS, ADDR_REGS, ADDR_REGS,
next prev parent reply other threads:[~2012-07-31 21:09 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-07-31 4:12 DJ Delorie
2012-07-31 16:55 ` Richard Henderson
2012-07-31 21:25 ` DJ Delorie [this message]
2012-07-31 22:22 ` Richard Henderson
2012-07-31 22:26 ` DJ Delorie
2012-07-31 22:47 ` Richard Henderson
2012-07-31 23:22 ` DJ Delorie
2012-07-31 23:21 ` Richard Henderson
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=201207312109.q6VL9SCl027555@greed.delorie.com \
--to=dj@redhat.com \
--cc=gcc-patches@gcc.gnu.org \
--cc=rth@redhat.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.
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).