public inbox for glibc-bugs-regex@sourceware.org
help / color / mirror / Atom feed
* [Bug regex/5945] New: regoff_t wrong has posix type
@ 2008-03-16 14:02 vik at forgottenroots dot de
  2008-03-30  4:31 ` [Bug regex/5945] " drepper at redhat dot com
                   ` (3 more replies)
  0 siblings, 4 replies; 5+ messages in thread
From: vik at forgottenroots dot de @ 2008-03-16 14:02 UTC (permalink / raw)
  To: glibc-bugs-regex

The type regoff_t should hold at least the same amount of bytes as off_t and
ssize_t 
here: http://www.opengroup.org/onlinepubs/009695399/basedefs/regex.h.html
It's defined in regex.h as 'int` so it won't hold off_t on a 64bit machine or a
32bit machine where off_t 64bit support is enabled (#define _FILE_OFFSET_BITS 64)

-- 
           Summary: regoff_t wrong has posix type
           Product: glibc
           Version: unspecified
            Status: NEW
          Severity: enhancement
          Priority: P2
         Component: regex
        AssignedTo: drepper at redhat dot com
        ReportedBy: vik at forgottenroots dot de
                CC: glibc-bugs-regex at sources dot redhat dot com,glibc-
                    bugs at sources dot redhat dot com


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.


^ permalink raw reply	[flat|nested] 5+ messages in thread

* [Bug regex/5945] regoff_t wrong has posix type
  2008-03-16 14:02 [Bug regex/5945] New: regoff_t wrong has posix type vik at forgottenroots dot de
@ 2008-03-30  4:31 ` drepper at redhat dot com
  2008-08-18 10:10 ` bonzini at gnu dot org
                   ` (2 subsequent siblings)
  3 siblings, 0 replies; 5+ messages in thread
From: drepper at redhat dot com @ 2008-03-30  4:31 UTC (permalink / raw)
  To: glibc-bugs-regex


------- Additional Comments From drepper at redhat dot com  2008-03-30 04:30 -------
This is known but obviously cannot easily be fixed.  Suspended until somebody
takes this serious to actually take a stab at a solution.

-- 
           What    |Removed                     |Added
----------------------------------------------------------------------------
             Status|NEW                         |SUSPENDED


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.


^ permalink raw reply	[flat|nested] 5+ messages in thread

* [Bug regex/5945] regoff_t wrong has posix type
  2008-03-16 14:02 [Bug regex/5945] New: regoff_t wrong has posix type 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
  3 siblings, 0 replies; 5+ messages in thread
From: bonzini at gnu dot org @ 2008-08-18 10:10 UTC (permalink / raw)
  To: glibc-bugs-regex


------- Additional Comments From bonzini at gnu dot org  2008-08-18 10:09 -------
You mean, it cannot be easily fixed because it breaks the ABI?

-- 


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.


^ permalink raw reply	[flat|nested] 5+ messages in thread

* [Bug regex/5945] regoff_t wrong has posix type
  2008-03-16 14:02 [Bug regex/5945] New: regoff_t wrong has posix type 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
  3 siblings, 0 replies; 5+ messages in thread
From: drepper at redhat dot com @ 2008-08-18 14:05 UTC (permalink / raw)
  To: glibc-bugs-regex


------- Additional Comments From drepper at redhat dot com  2008-08-18 14:04 -------
(In reply to comment #2)
> You mean, it cannot be easily fixed because it breaks the ABI?

Yes.

-- 


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.


^ permalink raw reply	[flat|nested] 5+ messages in thread

* [Bug regex/5945] regoff_t wrong has posix type
  2008-03-16 14:02 [Bug regex/5945] New: regoff_t wrong has posix type vik at forgottenroots dot de
                   ` (2 preceding siblings ...)
  2008-08-18 14:05 ` drepper at redhat dot com
@ 2010-09-09 15:44 ` bonzini at gnu dot org
  3 siblings, 0 replies; 5+ messages in thread
From: bonzini at gnu dot org @ 2010-09-09 15:44 UTC (permalink / raw)
  To: glibc-bugs-regex


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


^ permalink raw reply	[flat|nested] 5+ messages in thread

end of thread, other threads:[~2010-09-09 15:44 UTC | newest]

Thread overview: 5+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2008-03-16 14:02 [Bug regex/5945] New: regoff_t wrong has posix type 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 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).