public inbox for glibc-bugs-regex@sourceware.org
help / color / mirror / Atom feed
From: "bonzini at gnu dot org" <sourceware-bugzilla@sourceware.org>
To: glibc-bugs-regex@sources.redhat.com
Subject: [Bug regex/5945] regoff_t wrong has posix type
Date: Thu, 09 Sep 2010 15:44:00 -0000	[thread overview]
Message-ID: <20100909154442.17457.qmail@sourceware.org> (raw)
In-Reply-To: <20080316140107.5945.vik@forgottenroots.de>


------- Additional Comments From bonzini at gnu dot org  2010-09-09 15:44 -------
On bug-gnulib, the following suggestion was made by Bruno Haible:

> [glibc could] offer some preprocessor macro that makes regoff_t 64-bit wide -
> like it was done for off_t.
> 
> Would glibc need to export additional symbols for this? Yes.
> 
> Would a compiled glibc need to contain two copies of the regex code? No, the
> 32-bit version could be a thin wrapper around the 64-bit version.

I guess this would count as "somebody takes this serious to actually take a stab
at a solution".  Would _REGEX_OFFSET_BITS be okay for you as a macro?

-- 


http://sourceware.org/bugzilla/show_bug.cgi?id=5945

------- You are receiving this mail because: -------
You are on the CC list for the bug, or are watching someone who is.


  parent reply	other threads:[~2010-09-09 15:44 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-03-16 14:02 [Bug regex/5945] New: " vik at forgottenroots dot de
2008-03-30  4:31 ` [Bug regex/5945] " drepper at redhat dot com
2008-08-18 10:10 ` bonzini at gnu dot org
2008-08-18 14:05 ` drepper at redhat dot com
2010-09-09 15:44 ` bonzini at gnu dot org [this message]
     [not found] <bug-5945-132@http.sourceware.org/bugzilla/>
2011-06-17 10:43 ` bonzini at gnu dot org
2013-02-08  1:52 ` eggert at gnu dot org
2013-02-08  2:32 ` bugdal at aerifal dot cx
2014-06-27 13:08 ` fweimer at redhat dot com
2015-06-25 16:50 ` filbranden at google dot com

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=20100909154442.17457.qmail@sourceware.org \
    --to=sourceware-bugzilla@sourceware.org \
    --cc=glibc-bugs-regex@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).