musl mailing list - 2025/06

Follow @Openwall on Twitter for new release announcements and other news

[<prev month] [year] [list]

musl mailing list - 2025/06

Mon	Tue	Wed	Thu	Fri	Sat	Sun
						¹ 1
² 3	³ 2	⁴ 1	⁵ 10	⁶ 13	⁷	⁸ 8
⁹ 3	¹⁰ 1	¹¹ 2	¹² 13	¹³ 1	¹⁴ 1	¹⁵ 2
¹⁶ 13	¹⁷ 9	¹⁸ 16	¹⁹ 21	²⁰ 3	²¹	²²
²³	²⁴	²⁵	²⁶	²⁷	²⁸	²⁹
³⁰

Messages by day:

June 1 (1 message)

[PATCH] sigaction: don't sign-extend sa_flags (наб <nabijaczleweli@...ijaczleweli.xyz>)

June 2 (3 messages)

[PATCH] getopt: use LCTRANS macro instead of hidden symbol (Pablo Correa Gómez <pabloyoyoista@...tmarketos.org>)
Planned locale work and community thoughts (Pablo Correa Gomez <pabloyoyoista@...tmarketos.org>)
Possible issue formatting epoch time with strftime() (David Steele <david@...ackrest.org>)

June 3 (2 messages)

Re: Possible issue formatting epoch time with strftime() (Markus Wichmann <nullplan@....net>)
Re: Possible issue formatting epoch time with strftime() (David Steele <david@...ackrest.org>)

June 4 (1 message)

Re: c23 memset_explicit() (enh <enh@...gle.com>)

June 5 (10 messages)

Re: c23 memset_explicit() (Rich Felker <dalias@...c.org>)
Re: Possible issue formatting epoch time with strftime() (Rich Felker <dalias@...c.org>)
Re: Sign conversion warning in FD_ISSET() (David Steele <david@...ackrest.org>)
Re: Sign conversion warning in FD_ISSET() (Rich Felker <dalias@...c.org>)
Re: Sign conversion warning in FD_ISSET() (Thorsten Glaser <tg@...bsd.de>)
Re: Sign conversion warning in FD_ISSET() (David Steele <david@...ackrest.org>)
Re: Sign conversion warning in FD_ISSET() (Andy Caldwell <andy.m.caldwell@...glemail.com>)
Re: Sign conversion warning in FD_ISSET() (Rich Felker <dalias@...c.org>)
Re: Sign conversion warning in FD_ISSET() (Rich Felker <dalias@...c.org>)
Re: Sign conversion warning in FD_ISSET() (Brad House <brad@...d-house.com>)

June 6 (13 messages)

Re: Sign conversion warning in FD_ISSET() (Andy Caldwell <andy.m.caldwell@...glemail.com>)
Re: Sign conversion warning in FD_ISSET() (Rich Felker <dalias@...c.org>)
Re: Sign conversion warning in FD_ISSET() (Nick Wellnhofer <wellnhofer@...um.de>)
Re: Sign conversion warning in FD_ISSET() (Andy Caldwell <andy.m.caldwell@...glemail.com>)
Re: Sign conversion warning in FD_ISSET() (Rich Felker <dalias@...c.org>)
Re: Possible issue formatting epoch time with strftime() (Markus Wichmann <nullplan@....net>)
[PATCH] strptime: support "Z" value for the %z field descriptor (Rafał Miłecki <zajec5@...il.com>)
Re: [PATCH] strptime: support "Z" value for the %z field descriptor (Rich Felker <dalias@...ifal.cx>)
Re: [PATCH] strptime: support "Z" value for the %z field descriptor (enh <enh@...gle.com>)
Re: Sign conversion warning in FD_ISSET() (Andy Caldwell <andy.m.caldwell@...glemail.com>)
Re: Sign conversion warning in FD_ISSET() (Rich Felker <dalias@...c.org>)
Re: Sign conversion warning in FD_ISSET() (Andy Caldwell <andy.m.caldwell@...glemail.com>)
Re: [PATCH] strptime: support "Z" value for the %z field descriptor (Thorsten Glaser <tg@...bsd.de>)

June 8 (8 messages)

The `sigpause` function behavior does not fully comply with the POSIX specification (Tommy <tommyskypromax@...il.com>)
Re: The `sigpause` function behavior does not fully comply with the POSIX specification ("Haelwenn (lanodan) Monnier" <haelwenn@...udsdale.the-delta.net.eu.org…)
Re: The `sigpause` function behavior does not fully comply with the POSIX specification (Bobby Bingham <koorogi@...rogi.info>)
Re: The `sigpause` function behavior does not fully comply with the POSIX specification (Rich Felker <dalias@...c.org>)
Re: The `sigpause` function behavior does not fully comply with the POSIX specification (Bobby Bingham <koorogi@...rogi.info>)
Re: The `sigpause` function behavior does not fully comply with the POSIX specification (Rich Felker <dalias@...c.org>)
Re: The `sigpause` function behavior does not fully comply with the POSIX specification (Thorsten Glaser <tg@...lvis.org>)
Re: The `sigpause` function behavior does not fully comply with the POSIX specification (Markus Wichmann <nullplan@....net>)

June 9 (3 messages)

Re: The `sigpause` function behavior does not fully comply with the POSIX specification (Valery Ushakov <uwe@...err.spb.ru>)
Re: Re: The `sigpause` function behavior does not fully comply with the POSIX specification (Rich Felker <dalias@...c.org>)
Re: Re: The `sigpause` function behavior does not fully comply with the POSIX specification (Thorsten Glaser <tg@...lvis.org>)

June 10 (1 message)

Re: Re: The `sigpause` function behavior does not fully comply with the POSIX specification (Valery Ushakov <uwe@...err.spb.ru>)

June 11 (2 messages)

Locale project/LC_COLLATE update: NFD! (Rich Felker <dalias@...c.org>)
Re: Locale project/LC_COLLATE update: NFD! (Rich Felker <dalias@...c.org>)

June 12 (13 messages)

Collation table data format, round 1 (Rich Felker <dalias@...c.org>)
sys/prctl.h differences vs man page (Sebastian Andrzej Siewior <bigeasy@...utronix.de>)
Re: sys/prctl.h differences vs man page (enh <enh@...gle.com>)
Re: sys/prctl.h differences vs man page (Rich Felker <dalias@...c.org>)
Re: sys/prctl.h differences vs man page (enh <enh@...gle.com>)
Re: sys/prctl.h differences vs man page ("A. Wilcox" <AWilcox@...cox-Tech.com>)
Re: sys/prctl.h differences vs man page (Rich Felker <dalias@...c.org>)
Re: sys/prctl.h differences vs man page (Thorsten Glaser <tg@...bsd.de>)
Re: sys/prctl.h differences vs man page (Rich Felker <dalias@...c.org>)
Re: sys/prctl.h differences vs man page (Sebastian Andrzej Siewior <bigeasy@...utronix.de>)
Re: sys/prctl.h differences vs man page (Rich Felker <dalias@...c.org>)
Re: sys/prctl.h differences vs man page (Alejandro Colomar <alx@...nel.org>)
Re: sys/prctl.h differences vs man page (Alejandro Colomar <alx@...nel.org>)

June 13 (1 message)

Re: sys/prctl.h differences vs man page (Arnaldo Carvalho de Melo <acme@...nel.org>)

June 14 (1 message)

On current (and future) use of LCTRANS (Pablo Correa Gomez <pabloyoyoista@...tmarketos.org>)

June 15 (2 messages)

Re: On current (and future) use of LCTRANS (Markus Wichmann <nullplan@....net>)
Re: On current (and future) use of LCTRANS (Rich Felker <dalias@...c.org>)

June 16 (13 messages)

BUG: realloc(p,0) should be consistent with malloc(0) (Alejandro Colomar <alx@...nel.org>)
Re: BUG: realloc(p,0) should be consistent with malloc(0) (Rich Felker <dalias@...c.org>)
Re: BUG: realloc(p,0) should be consistent with malloc(0) (Alejandro Colomar <alx@...nel.org>)
Re: BUG: realloc(p,0) should be consistent with malloc(0) (enh <enh@...gle.com>)
Re: BUG: realloc(p,0) should be consistent with malloc(0) (Paul Eggert <eggert@...ucla.edu>)
Re: BUG: realloc(p,0) should be consistent with malloc(0) (Adhemerval Zanella Netto <adhemerval.zanella@...aro.org>)
Re: BUG: realloc(p,0) should be consistent with malloc(0) (Florian Weimer <fweimer@...hat.com>)
Re: BUG: realloc(p,0) should be consistent with malloc(0) (Adhemerval Zanella Netto <adhemerval.zanella@...aro.org>)
Re: BUG: realloc(p,0) should be consistent with malloc(0) (Alejandro Colomar <alx@...nel.org>)
Re: BUG: realloc(p,0) should be consistent with malloc(0) (Alejandro Colomar <alx@...nel.org>)
Re: BUG: realloc(p,0) should be consistent with malloc(0) (Alejandro Colomar <alx@...nel.org>)
Re: BUG: realloc(p,0) should be consistent with malloc(0) (Alejandro Colomar <alx@...nel.org>)
Re: BUG: realloc(p,0) should be consistent with malloc(0) (Joseph Myers <josmyers@...hat.com>)

June 17 (9 messages)

Re: BUG: realloc(p,0) should be consistent with malloc(0) (enh <enh@...gle.com>)
Re: BUG: realloc(p,0) should be consistent with malloc(0) (Florian Weimer <fweimer@...hat.com>)
Re: Re: BUG: realloc(p,0) should be consistent with malloc(0) (Rich Felker <dalias@...c.org>)
Re: Re: BUG: realloc(p,0) should be consistent with malloc(0) (Paul Eggert <eggert@...ucla.edu>)
Re: Re: BUG: realloc(p,0) should be consistent with malloc(0) (enh <enh@...gle.com>)
Re: Re: BUG: realloc(p,0) should be consistent with malloc(0) (Rich Felker <dalias@...c.org>)
Re[2]: Re: BUG: realloc(p,0) should be consistent with malloc(0) ("Laurent Bercot" <ska-dietlibc@...rnet.org>)
Re[2]: Re: BUG: realloc(p,0) should be consistent with malloc(0) ("Laurent Bercot" <ska-dietlibc@...rnet.org>)
Re: Re: BUG: realloc(p,0) should be consistent with malloc(0) (Alejandro Colomar <alx@...nel.org>)

June 18 (16 messages)

Re: [PATCH] LoongArch64: add new reloc types and NT_LOONGARCH_HW_* into elf.h (Yao Zi <ziyao@...root.org>)
Re: [PATCH] time.h: drop non-standard and out-of-date CLOCK_SGI_CYCLE (Yao Zi <ziyao@...root.org>)
Re: [PATCH] LoongArch64: add new reloc types and NT_LOONGARCH_HW_* into elf.h (Rich Felker <dalias@...c.org>)
Re: [PATCH] LoongArch64: add new reloc types and NT_LOONGARCH_HW_* into elf.h (Yao Zi <ziyao@...root.org>)
Re: [PATCH] LoongArch64: add new reloc types and NT_LOONGARCH_HW_* into elf.h (lixing <lixing@...ngson.cn>)
Re: Re: BUG: realloc(p,0) should be consistent with malloc(0) (enh <enh@...gle.com>)
Re: Re: BUG: realloc(p,0) should be consistent with malloc(0) (Thorsten Glaser <tg@...bsd.de>)
Re: BUG: realloc(p,0) should be consistent with malloc(0) (Andreas Schwab <schwab@...e.de>)
Re: Re: BUG: realloc(p,0) should be consistent with malloc(0) (enh <enh@...gle.com>)
Re: Re: BUG: realloc(p,0) should be consistent with malloc(0) (Rich Felker <dalias@...c.org>)
Re: BUG: realloc(p,0) should be consistent with malloc(0) (Alejandro Colomar <alx@...nel.org>)
Re: Re: BUG: realloc(p,0) should be consistent with malloc(0) (Alejandro Colomar <alx@...nel.org>)
Re: Planned locale work and community thoughts (Rich Felker <dalias@...c.org>)
Re: Planned locale work and community thoughts (Rich Felker <dalias@...c.org>)
Re: Planned locale work and community thoughts (Thorsten Glaser <tg@...bsd.de>)
Re: Planned locale work and community thoughts (Rich Felker <dalias@...c.org>)

June 19 (21 messages)

malloc.3: Clarify realloc(3) standards conformance (Alejandro Colomar <alx@...nel.org>)
Re: malloc.3: Clarify realloc(3) standards conformance (Collin Funk <collin.funk1@...il.com>)
Re: malloc.3: Clarify realloc(3) standards conformance (Alejandro Colomar <alx@...nel.org>)
Re: malloc.3: Clarify realloc(3) standards conformance (Rich Felker <dalias@...c.org>)
Re: malloc.3: Clarify realloc(3) standards conformance (Alejandro Colomar <alx@...nel.org>)
Re: malloc.3: Clarify realloc(3) standards conformance (Vincent Lefevre <vincent@...c17.net>)
Re: malloc.3: Clarify realloc(3) standards conformance (Rich Felker <dalias@...c.org>)
Re: malloc.3: Clarify realloc(3) standards conformance (Alejandro Colomar <alx@...nel.org>)
Re: malloc.3: Clarify realloc(3) standards conformance (Rich Felker <dalias@...c.org>)
Re: malloc.3: Clarify realloc(3) standards conformance (Alejandro Colomar <alx@...nel.org>)
[v2] malloc.3: Clarify realloc(3) standards conformance (Alejandro Colomar <alx@...nel.org>)
Re: [v2] malloc.3: Clarify realloc(3) standards conformance (Rich Felker <dalias@...c.org>)
Re: [v2] malloc.3: Clarify realloc(3) standards conformance (Thorsten Glaser <tg@...bsd.de>)
Re: Re: BUG: realloc(p,0) should be consistent with malloc(0) (Eric Blake <eblake@...hat.com>)
Re: [v2] malloc.3: Clarify realloc(3) standards conformance (Eric Blake <eblake@...hat.com>)
Re: [v2] malloc.3: Clarify realloc(3) standards conformance (Eric Blake <eblake@...hat.com>)
Re: [v2] malloc.3: Clarify realloc(3) standards conformance (Rich Felker <dalias@...c.org>)
Re: [v2] malloc.3: Clarify realloc(3) standards conformance (Thorsten Glaser <tg@...bsd.de>)
Re: Re: BUG: realloc(p,0) should be consistent with malloc(0) (Alejandro Colomar <alx@...nel.org>)
Re: Re: BUG: realloc(p,0) should be consistent with malloc(0) (Alejandro Colomar <alx@...nel.org>)
Re: Re: BUG: realloc(p,0) should be consistent with malloc(0) (Alejandro Colomar <alx@...nel.org>)

June 20 (3 messages)

Re: [v2] malloc.3: Clarify realloc(3) standards conformance (Alejandro Colomar <alx@...nel.org>)
Re: Re: BUG: realloc(p,0) should be consistent with malloc(0) (Vincent Lefevre <vincent@...c17.net>)
Re: Re: BUG: realloc(p,0) should be consistent with malloc(0) (Paul Eggert <eggert@...ucla.edu>)

123 messages

Powered by blists - more mailing lists

Confused about mailing lists and their use? Read about mailing lists on Wikipedia and check out these guidelines on proper formatting of your messages.