From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 17506 invoked by alias); 9 Sep 2010 15:44:53 -0000 Received: (qmail 17459 invoked by uid 48); 9 Sep 2010 15:44:42 -0000 Date: Thu, 09 Sep 2010 15:44:00 -0000 Message-ID: <20100909154442.17457.qmail@sourceware.org> From: "bonzini at gnu dot org" To: glibc-bugs-regex@sources.redhat.com In-Reply-To: <20080316140107.5945.vik@forgottenroots.de> References: <20080316140107.5945.vik@forgottenroots.de> Reply-To: sourceware-bugzilla@sourceware.org Subject: [Bug regex/5945] regoff_t wrong has posix type X-Bugzilla-Reason: CC Mailing-List: contact glibc-bugs-regex-help@sourceware.org; run by ezmlm Precedence: bulk List-Id: List-Subscribe: List-Post: List-Help: , Sender: glibc-bugs-regex-owner@sourceware.org X-SW-Source: 2010-09/txt/msg00001.txt.bz2 ------- 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.