From: Mike Frysinger <vapier@gentoo.org>
To: "H.J. Lu" <hjl.tools@gmail.com>
Cc: Mark Wielaard <mjw@redhat.com>,
Joel Brobecker <brobecker@adacore.com>,
GCC Patches <gcc-patches@gcc.gnu.org>,
Binutils <binutils@sourceware.org>,
GDB <gdb-patches@sourceware.org>
Subject: Re: ping #3: [RFA] Add --with-libz-prefix option in config/zlib.m4
Date: Wed, 18 Feb 2015 23:10:00 -0000 [thread overview]
Message-ID: <20150218231032.GZ544@vapier> (raw)
In-Reply-To: <CAMe9rOqd4Tzf0Kcaz91-eVYOOb8msna65m1qLFrnOXRmKLSa3A@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 1913 bytes --]
On 18 Feb 2015 14:24, H.J. Lu wrote:
> On Wed, Feb 18, 2015 at 2:21 PM, Mike Frysinger wrote:
> > i think we already have the reports: multiple people don't think it should be
> > (1) x86-specific or (2) required. don't get me wrong -- i think having support
> > like this is great. that doesn't mean we should be forcing it.
>
> Please file a bug report with a testcase.
this is getting kafka-esque. you yourself stated:
On Linux/x86, zlib is required for assembler. At least, you should issue an
error when --without-libz is used in binutils for Linux/x86 target.
that should not be the case. making someone open a bug report so you can close
it with "fixed" and a patch is wasting time. just fix it now.
all that said, if we look at your actual commit (89e7505fcde4bd83948f559f429a0):
gas/config/tc-i386.c:
+#ifdef TE_LINUX
+/* Default to compress debug sections for Linux. */
+int flag_compress_debug = 1;
+#endif
and we look at where that flag is used:
gas/as.c:
...
case OPTION_COMPRESS_DEBUG:
#ifdef HAVE_ZLIB_H
flag_compress_debug = 1;
#else
as_warn (_("cannot compress debug sections (zlib not installed)"));
#endif /* HAVE_ZLIB_H */
break;
case OPTION_NOCOMPRESS_DEBUG:
flag_compress_debug = 0;
break;
...
gas/write.c:
void
write_object_file (void)
{
...
if (flag_compress_debug)
bfd_map_over_sections (stdoutput, compress_debug, (char *) 0);
...
static void
compress_debug (bfd *abfd, asection *sec, void *xxx ATTRIBUTE_UNUSED)
{
...
strm = compress_init ();
if (strm == NULL)
return;
it turns out the current code does *not* require zlib. as long as that does not
change (either issuing a warning or throwing an error), i see no reason why we
need or should make zlib a requirement in binutils, regardless of target.
-mike
[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 819 bytes --]
next prev parent reply other threads:[~2015-02-18 23:10 UTC|newest]
Thread overview: 28+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-01-07 14:46 Joel Brobecker
2015-01-07 16:01 ` Tristan Gingold
2015-01-07 17:02 ` Joel Brobecker
2015-02-19 7:55 ` Thomas Schwinge
2015-02-19 7:58 ` Thomas Schwinge
2015-01-21 7:49 ` ping: " Joel Brobecker
2015-01-21 8:22 ` Tristan Gingold
2015-01-21 8:33 ` Joel Brobecker
2015-02-04 3:57 ` ping^2: " Joel Brobecker
2015-02-18 12:09 ` ping #3: " Joel Brobecker
2015-02-18 12:56 ` H.J. Lu
2015-02-18 16:55 ` Mike Frysinger
2015-02-18 16:58 ` H.J. Lu
2015-02-18 19:44 ` Mike Frysinger
2015-02-18 19:52 ` H.J. Lu
2015-02-18 20:32 ` Mark Wielaard
2015-02-18 20:42 ` Jakub Jelinek
2015-02-18 20:53 ` H.J. Lu
2015-02-18 21:54 ` Mark Wielaard
2015-02-18 22:03 ` H.J. Lu
2015-02-18 22:21 ` Mike Frysinger
2015-02-18 22:24 ` H.J. Lu
2015-02-18 23:10 ` Mike Frysinger [this message]
2015-02-19 7:17 ` Mark Wielaard
2015-02-19 13:52 ` H.J. Lu
2015-02-20 8:01 ` Mark Wielaard
2015-02-18 17:00 ` Joel Sherrill
2015-02-19 2:42 ` Joel Brobecker
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=20150218231032.GZ544@vapier \
--to=vapier@gentoo.org \
--cc=binutils@sourceware.org \
--cc=brobecker@adacore.com \
--cc=gcc-patches@gcc.gnu.org \
--cc=gdb-patches@sourceware.org \
--cc=hjl.tools@gmail.com \
--cc=mjw@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