public inbox for
 help / color / mirror / Atom feed
From: Markus Trippelsdorf <>
To: Joseph Myers <>
Cc: Matthias Klose <>, GCC Patches <>
Subject: Re: [patch] build xz (instead of bz2) compressed tarballs and diffs
Date: Mon, 15 May 2017 14:15:00 -0000	[thread overview]
Message-ID: <20170515141344.GB27845@x4> (raw)
In-Reply-To: <>

On 2017.05.15 at 14:02 +0000, Joseph Myers wrote:
> The xz manpage warns against blindly using -9 (for which --best is a 
> deprecated alias) because of the implications for memory requirements for 
> decompressing.  If there's a reason it's considered appropriate here, I 
> think it needs an explanatory comment.

I think it is unacceptable, because it would increase memory usage when
decompressing over 20x compared to bz2 (and over 100x while compressing).

The default -6 should be good enough (3x more memory when decompressing).


  reply	other threads:[~2017-05-15 14:13 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-05-15  1:35 Matthias Klose
2017-05-15 14:11 ` Joseph Myers
2017-05-15 14:15   ` Markus Trippelsdorf [this message]
2017-05-15 18:38     ` Jakub Jelinek
2017-05-15 19:13       ` Markus Trippelsdorf
2017-05-23 23:22         ` Matthias Klose
2017-05-18 10:41 ` Richard Biener
2017-05-23 23:56   ` Matthias Klose
2017-05-24  7:23     ` Richard Biener
2017-05-24 19:21     ` Gerald Pfeifer

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:

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20170515141344.GB27845@x4 \ \ \ \ \

* 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).