From: Jeff Law <law@redhat.com>
To: David Edelsohn <dje.gcc@gmail.com>,
Ilya Enkovich <enkovich.gnu@gmail.com>
Cc: GCC Patches <gcc-patches@gcc.gnu.org>
Subject: Re: [PATCH, Pointer Bounds Checker, Builtins instrumentation 3/5] Expand instrumented builtin calls
Date: Tue, 18 Nov 2014 03:00:00 -0000 [thread overview]
Message-ID: <546AB3F7.4060601@redhat.com> (raw)
In-Reply-To: <CAGWvny=rF0J-wcD=ddT7LngzpZCDTj4x1ALE-fdwAq6KJ4KD4g@mail.gmail.com>
On 11/17/14 18:18, David Edelsohn wrote:
>> I'll try to make a patch reducing amound of builtin codes to a
>> required minimum in case it appears to be the best option we have.
>
> I am not a stabstring expert, but the output that I am seeing in
> almost every assembler file and the output that is overflowing the
> file is:
Seeing this reminded me that, IIRC, we had some hacks to deal with
insanely long stab strings in the past... And a bit of reading
dbxout.c reminds me it was DBX_CONTIN_LENGTH.
Presumably some of the xcoff bits aren't honoring DBX_CONTIN_LENGTH or
maybe it just needs to be defined...
Jeff
next prev parent reply other threads:[~2014-11-18 2:50 UTC|newest]
Thread overview: 28+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-11-17 18:41 David Edelsohn
2014-11-17 19:07 ` Jeff Law
2014-11-17 19:12 ` David Edelsohn
2014-11-17 20:06 ` Mike Stump
2014-11-17 20:36 ` Jeff Law
2014-11-17 21:13 ` Ilya Enkovich
2014-11-18 0:53 ` Joseph Myers
2014-11-18 2:06 ` David Edelsohn
2014-11-18 3:00 ` Jeff Law [this message]
2014-11-18 2:46 ` David Edelsohn
2014-11-18 2:56 ` Jeff Law
2014-11-18 3:01 ` Jeff Law
2014-11-18 10:57 ` Ilya Enkovich
2014-11-18 12:18 ` Richard Biener
2014-11-18 12:34 ` Ilya Enkovich
2014-11-18 12:38 ` Richard Biener
2014-11-18 13:42 ` Ilya Enkovich
2014-11-18 14:07 ` David Edelsohn
2014-11-18 14:33 ` Richard Biener
2014-11-18 14:42 ` David Edelsohn
2014-11-18 19:09 ` Jeff Law
2014-11-18 19:12 ` David Edelsohn
2014-11-17 20:26 ` Ilya Enkovich
2014-11-18 3:14 ` Jeff Law
2014-11-18 10:05 ` Richard Biener
2014-11-18 16:33 ` Jeff Law
-- strict thread matches above, loose matches on Subject: below --
2014-11-06 12:25 Ilya Enkovich
2014-11-14 7:06 ` Jeff Law
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=546AB3F7.4060601@redhat.com \
--to=law@redhat.com \
--cc=dje.gcc@gmail.com \
--cc=enkovich.gnu@gmail.com \
--cc=gcc-patches@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).