From: Martin Dalecki <dalecki@evision-ventures.com>
To: Jakob Kemi <jakob.kemi@telia.com>
Cc: linux-kernel@vger.kernel.org
Subject: Re: [PATCH] hex <-> int conversion routines.
Date: Wed, 20 Feb 2002 11:25:13 +0100 [thread overview]
Message-ID: <3C737989.8040306@evision-ventures.com> (raw)
In-Reply-To: <02021915240900.00635@jakob> <3C7274BE.1030803@evision-ventures.com> <02021919493204.00447@jakob>
>>>+static __inline__ char inthex_nibble(int x)
>>>+{
>>>+ const char* digits = "0123456789abcdef";
>>>+
>>>+ return digits[x & 0x0f];
>>>+}
>>>
>>perhaps better do static const char *digits.
>>
> GCC doesn't copy const strings, as opposed to other const arrays.
Currently.
> So it should be fine as it is. GCC also reuse duplicated strings.
next prev parent reply other threads:[~2002-02-20 10:26 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-02-19 15:39 [PATCH] hex <-> int conversion routines Jakob Kemi
2002-02-19 15:52 ` Martin Dalecki
2002-02-19 18:49 ` Jakob Kemi
2002-02-19 19:02 ` Bernd Petrovitsch
2002-02-19 20:27 ` H. Peter Anvin
2002-02-23 2:30 ` Ian Molton
2002-02-19 19:04 ` H. Peter Anvin
2002-02-20 10:25 ` Martin Dalecki [this message]
2002-02-19 16:51 ` Richard B. Johnson
2002-02-19 18:02 ` Linus Torvalds
2002-02-19 20:29 ` george anzinger
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=3C737989.8040306@evision-ventures.com \
--to=dalecki@evision-ventures.com \
--cc=jakob.kemi@telia.com \
--cc=linux-kernel@vger.kernel.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