From: Alexandre Oliva <aoliva@redhat.com>
To: binutils@sources.redhat.com
Subject: Re: limit overflow errors to something sensible
Date: Sun, 04 May 2003 21:25:00 -0000 [thread overview]
Message-ID: <or65oqwgip.fsf@free.redhat.lsd.ic.unicamp.br> (raw)
In-Reply-To: <oristlerfv.fsf@free.redhat.lsd.ic.unicamp.br>
On Apr 10, 2003, Alexandre Oliva <aoliva@redhat.com> wrote:
> Index: ld/ChangeLog
> from Alexandre Oliva <aoliva@redhat.com>
> * ldmain.h (overflow_cutoff_limit): Declare.
> * ldmain.c (overflow_cutoff_limit): Define, initialized to 10.
> (reloc_overflow): Limit error messages based on it.
> * lexsup.c (parse_args) <OPTION_VERBOSE>: Set cutoff to
> unlimited.
Ping?
--
Alexandre Oliva Enjoy Guarana', see http://www.ic.unicamp.br/~oliva/
Red Hat GCC Developer aoliva@{redhat.com, gcc.gnu.org}
CS PhD student at IC-Unicamp oliva@{lsd.ic.unicamp.br, gnu.org}
Free Software Evangelist Professional serial bug killer
next prev parent reply other threads:[~2003-05-04 21:25 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-04-11 1:47 Alexandre Oliva
2003-05-04 21:25 ` Alexandre Oliva [this message]
2003-05-05 5:22 ` Alan Modra
2003-05-07 4:13 ` Alexandre Oliva
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=or65oqwgip.fsf@free.redhat.lsd.ic.unicamp.br \
--to=aoliva@redhat.com \
--cc=binutils@sources.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).