From: "Frank Ch. Eigler" <fche@redhat.com>
To: Mike Frysinger <vapier@gentoo.org>
Cc: cgen@sourceware.org
Subject: Re: [PATCH] sim: tighten up generated decode tables
Date: Fri, 22 Dec 2023 11:12:09 -0500 [thread overview]
Message-ID: <20231222161209.GC29647@redhat.com> (raw)
In-Reply-To: <20231222010028.17297-1-vapier@gentoo.org>
Hi -
> The use of /* fall through */ with consective case statements doesn't
> really add any value, and when generating large files, can take up a
> lot of space. In the case of cris, it alone adds ~20k, or ~10%.
A few kilobytes is basically zero cost, isn't it?
- FChE
next prev parent reply other threads:[~2023-12-22 16:12 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-12-22 1:00 Mike Frysinger
2023-12-22 10:55 ` Jose E. Marchesi
2023-12-22 19:58 ` Mike Frysinger
2023-12-23 10:30 ` Jose E. Marchesi
2023-12-22 16:12 ` Frank Ch. Eigler [this message]
2023-12-22 19:55 ` Mike Frysinger
2023-12-22 20:05 ` Frank Ch. Eigler
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=20231222161209.GC29647@redhat.com \
--to=fche@redhat.com \
--cc=cgen@sourceware.org \
--cc=vapier@gentoo.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).