musl mailing list
Recent messages:
- 2025/06/30 #2:
Re: Paintcans for reverse iterating strings (Rich Felker <dalias@...c.org>)
- 2025/06/30 #1:
Re: alx-0029r6 - Restore the traditional realloc(3) specification (Alejandro Colomar <alx@...nel.org>)
- 2025/06/29 #14:
Re: Re: alx-0029r6 - Restore the traditional realloc(3)
specification (Rich Felker <dalias@...c.org>)
- 2025/06/29 #13:
Re: alx-0029r6 - Restore the traditional realloc(3) specification ("H. Peter Anvin" <hpa@...or.com>)
- 2025/06/29 #12:
Re: Paintcans for reverse iterating strings (Rich Felker <dalias@...c.org>)
- 2025/06/29 #11:
Re: alx-0029r6 - Restore the traditional realloc(3) specification (Alejandro Colomar <alx@...nel.org>)
- 2025/06/29 #10:
Re: Paintcans for reverse iterating strings (Nick Wellnhofer <wellnhofer@...um.de>)
- 2025/06/29 #9:
Re: Paintcans for reverse iterating strings (Rich Felker <dalias@...c.org>)
- 2025/06/29 #8:
Re: Paintcans for reverse iterating strings (Nick Wellnhofer <wellnhofer@...um.de>)
- 2025/06/29 #7:
Re: Paintcans for reverse iterating strings (Rich Felker <dalias@...c.org>)
- 2025/06/29 #6:
Re: Re:Paintcans for reverse iterating strings (Rich Felker <dalias@...c.org>)
- 2025/06/29 #5:
Re: Paintcans for reverse iterating strings (Joakim Sindholt <opensource@...sha.com>)
- 2025/06/29 #4:
Re:Paintcans for reverse iterating strings ("David Wang" <00107082@....com>)
- 2025/06/29 #3:
Re: Paintcans for reverse iterating strings (Alexander Monakov <amonakov@...ras.ru>)
- 2025/06/29 #2:
Re: Paintcans for reverse iterating strings (Rich Felker <dalias@...c.org>)
- 2025/06/29 #1:
Paintcans for reverse iterating strings (Rich Felker <dalias@...c.org>)
- 2025/06/28 #1:
ctanh - handling of largish arguments (Damian McGuckin <damianm@....com.au>)
- 2025/06/27 #16:
Re: Re: alx-0029r5 - Restore the traditional realloc(3)
specification (Rich Felker <dalias@...c.org>)
- 2025/06/27 #15:
Re: Re: alx-0029r5 - Restore the traditional realloc(3)
specification (Alejandro Colomar <alx@...nel.org>)
- 2025/06/27 #14:
Re: Re: alx-0029r5 - Restore the traditional realloc(3)
specification (Rich Felker <dalias@...c.org>)
- 2025/06/27 #13:
Re: alx-0029r5 - Restore the traditional realloc(3) specification (Alejandro Colomar <alx@...nel.org>)
- 2025/06/27 #12:
Re: alx-0029r5 - Restore the traditional realloc(3) specification (Joseph Myers <josmyers@...hat.com>)
- 2025/06/27 #11:
Re: alx-0029r5 - Restore the traditional realloc(3) specification (Martin Uecker <ma.uecker@...il.com>)
- 2025/06/27 #10:
Re: alx-0029r5 - Restore the traditional realloc(3) specification (Florian Weimer <fweimer@...hat.com>)
- 2025/06/27 #9:
Re: alx-0029r5 - Restore the traditional realloc(3) specification (Alejandro Colomar <alx@...nel.org>)
- 2025/06/27 #8:
Re: alx-0029r5 - Restore the traditional realloc(3) specification (Florian Weimer <fweimer@...hat.com>)
- 2025/06/27 #7:
alx-0029r6 - Restore the traditional realloc(3) specification (Alejandro Colomar <alx@...nel.org>)
- 2025/06/27 #6:
Re: alx-0029r5 - Restore the traditional realloc(3) specification (Alejandro Colomar <alx@...nel.org>)
- 2025/06/27 #5:
Re: alx-0029r5 - Restore the traditional realloc(3) specification (Alejandro Colomar <alx@...nel.org>)
- 2025/06/27 #4:
Re: alx-0029r5 - Restore the traditional realloc(3) specification (Florian Weimer <fweimer@...hat.com>)
- 2025/06/27 #3:
Re: Re: alx-0029r5 - Restore the traditional realloc(3) specification (Jens Gustedt <jens.gustedt@...ia.fr>)
- 2025/06/27 #2:
Re: alx-0029r5 - Restore the traditional realloc(3) specification (Alejandro Colomar <alx@...nel.org>)
- 2025/06/27 #1:
Re: alx-0029r5 - Restore the traditional realloc(3) specification (Mark Harris <mark.hsj@...il.com>)
- 2025/06/26 #1:
alx-0029r5 - Restore the traditional realloc(3) specification (Alejandro Colomar <alx@...nel.org>)
- 2025/06/25 #15:
Re: Re: alx-0029r4 - Restore the traditional realloc(3)
specification (Rich Felker <dalias@...c.org>)
- 2025/06/25 #14:
Re: alx-0029r4 - Restore the traditional realloc(3) specification (Wilco Dijkstra <Wilco.Dijkstra@....com>)
- 2025/06/25 #13:
Re: alx-0029r4 - Restore the traditional realloc(3) specification (Alejandro Colomar <alx@...nel.org>)
- 2025/06/25 #12:
Re: alx-0029r4 - Restore the traditional realloc(3) specification (Eric Blake <eblake@...hat.com>)
- 2025/06/25 #11:
Re: alx-0029r4 - Restore the traditional realloc(3) specification (Eric Blake <eblake@...hat.com>)
- 2025/06/25 #10:
Re: alx-0029r4 - Restore the traditional realloc(3) specification (Alejandro Colomar <alx@...nel.org>)
- 2025/06/25 #9:
Re: alx-0029r4 - Restore the traditional realloc(3) specification (Eric Blake <eblake@...hat.com>)
- 2025/06/25 #8:
Re: alx-0029r4 - Restore the traditional realloc(3) specification (Alejandro Colomar <alx@...nel.org>)
- 2025/06/25 #7:
Re: alx-0029r4 - Restore the traditional realloc(3) specification (Alejandro Colomar <alx@...nel.org>)
- 2025/06/25 #6:
Re: Re: alx-0029r3 - Restore the traditional realloc(3) specification (enh <enh@...gle.com>)
- 2025/06/25 #5:
Re: alx-0029r4 - Restore the traditional realloc(3) specification (Alejandro Colomar <alx@...nel.org>)
- 2025/06/25 #4:
Re: alx-0029r4 - Restore the traditional realloc(3) specification (Eric Blake <eblake@...hat.com>)
- 2025/06/25 #3:
alx-0029r4 - Restore the traditional realloc(3) specification (Alejandro Colomar <alx@...nel.org>)
- 2025/06/25 #2:
Re: Re: alx-0029r3 - Restore the traditional realloc(3)
specification (Rich Felker <dalias@...c.org>)
- 2025/06/25 #1:
Re: Re: alx-0029r3 - Restore the traditional realloc(3) specification (Jeffrey Walton <noloader@...il.com>)
- 2025/06/24 #10:
Re: alx-0029r3 - Restore the traditional realloc(3) specification (Alejandro Colomar <alx@...nel.org>)
- 2025/06/24 #9:
Re: alx-0029r3 - Restore the traditional realloc(3) specification (Eric Blake <eblake@...hat.com>)
- 2025/06/24 #8:
Re: alx-0029r3 - Restore the traditional realloc(3) specification (Eric Blake <eblake@...hat.com>)
- 2025/06/24 #7:
Re: [PATCH] endian.h: use parentheses to silence warnings (Rich Felker <dalias@...c.org>)
- 2025/06/24 #6:
[PATCH] endian.h: use parentheses to silence warnings (Jacob Abrams <satur9nine@...il.com>)
- 2025/06/24 #5:
Re: alx-0029r3 - Restore the traditional realloc(3) specification (Alejandro Colomar <alx@...nel.org>)
- 2025/06/24 #4:
Re: Re: alx-0029r3 - Restore the traditional realloc(3)
specification (Rich Felker <dalias@...c.org>)
- 2025/06/24 #3:
Re: alx-0029r3 - Restore the traditional realloc(3) specification (Bruno Haible <bruno@...sp.org>)
- 2025/06/24 #2:
Re: alx-0029r3 - Restore the traditional realloc(3) specification (Florian Weimer <fweimer@...hat.com>)
- 2025/06/24 #1:
alx-0029r3 - Restore the traditional realloc(3) specification (Alejandro Colomar <alx@...nel.org>)
- 2025/06/23 #1:
Re: Bug in reallocf(3) when calling realloc(3) (Rich Felker <dalias@...c.org>)
- 2025/06/22 #1:
Re: Bug in reallocf(3) when calling realloc(3) (Florian Weimer <fweimer@...hat.com>)
- 2025/06/21 #21:
Re: Bug in reallocf(3) when calling realloc(3) (Alejandro Colomar <alx@...nel.org>)
- 2025/06/21 #20:
Re: Bug in reallocf(3) when calling realloc(3) (Rich Felker <dalias@...c.org>)
- 2025/06/21 #19:
Bug in reallocf(3) when calling realloc(3) (Alejandro Colomar <alx@...nel.org>)
- 2025/06/21 #18:
Re: Re: alx-0029r1 - Restore the traditional realloc(3)
specification (Rich Felker <dalias@...c.org>)
- 2025/06/21 #17:
Re: Re: BUG: realloc(p,0) should be consistent with malloc(0) (Alejandro Colomar <alx@...nel.org>)
- 2025/06/21 #16:
Re: Re: BUG: realloc(p,0) should be consistent with malloc(0) (Adhemerval Zanella <adhemerval.zanella@...aro.org>)
- 2025/06/21 #15:
Re: Re: alx-0029r1 - Restore the traditional realloc(3)
specification (Markus Wichmann <nullplan@....net>)
- 2025/06/21 #14:
alx-0029r2 - Restore the traditional realloc(3) specification (Alejandro Colomar <alx@...nel.org>)
- 2025/06/21 #13:
Re: Re: BUG: realloc(p,0) should be consistent with malloc(0) (Sam James <sam@...too.org>)
- 2025/06/21 #12:
Re: Re: BUG: realloc(p,0) should be consistent with malloc(0) (Alejandro Colomar <alx@...nel.org>)
- 2025/06/21 #11:
Re: alx-0029r1 - Restore the traditional realloc(3) specification (Alejandro Colomar <alx@...nel.org>)
- 2025/06/21 #10:
Re: Re: BUG: realloc(p,0) should be consistent with malloc(0) (Sam James <sam@...too.org>)
- 2025/06/21 #9:
Re: alx-0029r1 - Restore the traditional realloc(3) specification (Paul Eggert <eggert@...ucla.edu>)
- 2025/06/21 #8:
Re: Re: alx-0029r1 - Restore the traditional realloc(3)
specification (Alejandro Colomar <alx@...nel.org>)
- 2025/06/21 #7:
Re: Re: alx-0029r1 - Restore the traditional realloc(3)
specification (Rich Felker <dalias@...c.org>)
- 2025/06/21 #6:
Re: Re: alx-0029r1 - Restore the traditional realloc(3)
specification (Rich Felker <dalias@...c.org>)
- 2025/06/21 #5:
Re: alx-0029r1 - Restore the traditional realloc(3) specification (Alejandro Colomar <alx@...nel.org>)
- 2025/06/21 #4:
Re: alx-0029r1 - Restore the traditional realloc(3) specification (Alejandro Colomar <alx@...nel.org>)
- 2025/06/21 #3:
Re: alx-0029r1 - Restore the traditional realloc(3) specification (Alejandro Colomar <alx@...nel.org>)
- 2025/06/21 #2:
Re: alx-0029r1 - Restore the traditional realloc(3) specification (Paul Eggert <eggert@...ucla.edu>)
- 2025/06/21 #1:
Re: alx-0029r1 - Restore the traditional realloc(3) specification (Alejandro Colomar <alx@...nel.org>)
- 2025/06/20 #17:
Re: alx-0029r1 - Restore the traditional realloc(3) specification ("Maciej W. Rozycki" <macro@...hat.com>)
- 2025/06/20 #16:
Re: alx-0029r1 - Restore the traditional realloc(3) specification (Christopher Bazley <chris.bazley.wg14@...il.com>)
- 2025/06/20 #15:
Re: alx-0029r1 - Restore the traditional realloc(3) specification (Thorsten Glaser <tg@...bsd.de>)
- 2025/06/20 #14:
Re: alx-0029r1 - Restore the traditional realloc(3) specification (Alejandro Colomar <alx@...nel.org>)
- 2025/06/20 #13:
alx-0029r1 - Restore the traditional realloc(3) specification (Alejandro Colomar <alx@...nel.org>)
- 2025/06/20 #12:
Re: Re: BUG: realloc(p,0) should be consistent with malloc(0) (Paul Eggert <eggert@...ucla.edu>)
- 2025/06/20 #11:
Re: Re: BUG: realloc(p,0) should be consistent with malloc(0) (Alejandro Colomar <alx@...nel.org>)
- 2025/06/20 #10:
Re: Re: BUG: realloc(p,0) should be consistent with malloc(0) (Eric Blake <eblake@...hat.com>)
- 2025/06/20 #9:
Re: Re: BUG: realloc(p,0) should be consistent with
malloc(0) (Joseph Myers <josmyers@...hat.com>)
- 2025/06/20 #8:
Re: Re: BUG: realloc(p,0) should be consistent with malloc(0) (Mark Harris <mark.hsj@...il.com>)
- 2025/06/20 #7:
Re: Re: BUG: realloc(p,0) should be consistent with malloc(0) (Alejandro Colomar <alx@...nel.org>)
- 2025/06/20 #6:
Re: Re: BUG: realloc(p,0) should be consistent with malloc(0) (Vincent Lefevre <vincent@...c17.net>)
- 2025/06/20 #5:
Re: Re: BUG: realloc(p,0) should be consistent with malloc(0) (Alejandro Colomar <alx@...nel.org>)
- 2025/06/20 #4:
Re: Re: BUG: realloc(p,0) should be consistent with malloc(0) (Vincent Lefevre <vincent@...c17.net>)
- 2025/06/20 #3:
Re: Re: BUG: realloc(p,0) should be consistent with malloc(0) (Paul Eggert <eggert@...ucla.edu>)
- 2025/06/20 #2:
Re: Re: BUG: realloc(p,0) should be consistent with malloc(0) (Vincent Lefevre <vincent@...c17.net>)
- 2025/06/20 #1:
Re: [v2] malloc.3: Clarify realloc(3) standards conformance (Alejandro Colomar <alx@...nel.org>)
- 2025/06/19 #21:
Re: Re: BUG: realloc(p,0) should be consistent with malloc(0) (Alejandro Colomar <alx@...nel.org>)
22179 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.