musl mailing list
Recent messages:
- 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>)
- 2025/06/19 #20:
Re: Re: BUG: realloc(p,0) should be consistent with malloc(0) (Alejandro Colomar <alx@...nel.org>)
- 2025/06/19 #19:
Re: Re: BUG: realloc(p,0) should be consistent with malloc(0) (Alejandro Colomar <alx@...nel.org>)
- 2025/06/19 #18:
Re: [v2] malloc.3: Clarify realloc(3) standards conformance (Thorsten Glaser <tg@...bsd.de>)
- 2025/06/19 #17:
Re: [v2] malloc.3: Clarify realloc(3) standards conformance (Rich Felker <dalias@...c.org>)
- 2025/06/19 #16:
Re: [v2] malloc.3: Clarify realloc(3) standards conformance (Eric Blake <eblake@...hat.com>)
- 2025/06/19 #15:
Re: [v2] malloc.3: Clarify realloc(3) standards conformance (Eric Blake <eblake@...hat.com>)
- 2025/06/19 #14:
Re: Re: BUG: realloc(p,0) should be consistent with malloc(0) (Eric Blake <eblake@...hat.com>)
- 2025/06/19 #13:
Re: [v2] malloc.3: Clarify realloc(3) standards conformance (Thorsten Glaser <tg@...bsd.de>)
- 2025/06/19 #12:
Re: [v2] malloc.3: Clarify realloc(3) standards conformance (Rich Felker <dalias@...c.org>)
- 2025/06/19 #11:
[v2] malloc.3: Clarify realloc(3) standards conformance (Alejandro Colomar <alx@...nel.org>)
- 2025/06/19 #10:
Re: malloc.3: Clarify realloc(3) standards conformance (Alejandro Colomar <alx@...nel.org>)
- 2025/06/19 #9:
Re: malloc.3: Clarify realloc(3) standards conformance (Rich Felker <dalias@...c.org>)
- 2025/06/19 #8:
Re: malloc.3: Clarify realloc(3) standards conformance (Alejandro Colomar <alx@...nel.org>)
- 2025/06/19 #7:
Re: malloc.3: Clarify realloc(3) standards conformance (Rich Felker <dalias@...c.org>)
- 2025/06/19 #6:
Re: malloc.3: Clarify realloc(3) standards conformance (Vincent Lefevre <vincent@...c17.net>)
- 2025/06/19 #5:
Re: malloc.3: Clarify realloc(3) standards conformance (Alejandro Colomar <alx@...nel.org>)
- 2025/06/19 #4:
Re: malloc.3: Clarify realloc(3) standards conformance (Rich Felker <dalias@...c.org>)
- 2025/06/19 #3:
Re: malloc.3: Clarify realloc(3) standards conformance (Alejandro Colomar <alx@...nel.org>)
- 2025/06/19 #2:
Re: malloc.3: Clarify realloc(3) standards conformance (Collin Funk <collin.funk1@...il.com>)
- 2025/06/19 #1:
malloc.3: Clarify realloc(3) standards conformance (Alejandro Colomar <alx@...nel.org>)
- 2025/06/18 #16:
Re: Planned locale work and community thoughts (Rich Felker <dalias@...c.org>)
- 2025/06/18 #15:
Re: Planned locale work and community thoughts (Thorsten Glaser <tg@...bsd.de>)
- 2025/06/18 #14:
Re: Planned locale work and community thoughts (Rich Felker <dalias@...c.org>)
- 2025/06/18 #13:
Re: Planned locale work and community thoughts (Rich Felker <dalias@...c.org>)
- 2025/06/18 #12:
Re: Re: BUG: realloc(p,0) should be consistent with malloc(0) (Alejandro Colomar <alx@...nel.org>)
- 2025/06/18 #11:
Re: BUG: realloc(p,0) should be consistent with malloc(0) (Alejandro Colomar <alx@...nel.org>)
- 2025/06/18 #10:
Re: Re: BUG: realloc(p,0) should be consistent with malloc(0) (Rich Felker <dalias@...c.org>)
- 2025/06/18 #9:
Re: Re: BUG: realloc(p,0) should be consistent with malloc(0) (enh <enh@...gle.com>)
- 2025/06/18 #8:
Re: BUG: realloc(p,0) should be consistent with malloc(0) (Andreas Schwab <schwab@...e.de>)
- 2025/06/18 #7:
Re: Re: BUG: realloc(p,0) should be consistent with
malloc(0) (Thorsten Glaser <tg@...bsd.de>)
- 2025/06/18 #6:
Re: Re: BUG: realloc(p,0) should be consistent with malloc(0) (enh <enh@...gle.com>)
- 2025/06/18 #5:
Re: [PATCH] LoongArch64: add new reloc types and
NT_LOONGARCH_HW_* into elf.h (lixing <lixing@...ngson.cn>)
- 2025/06/18 #4:
Re: [PATCH] LoongArch64: add new reloc types and
NT_LOONGARCH_HW_* into elf.h (Yao Zi <ziyao@...root.org>)
- 2025/06/18 #3:
Re: [PATCH] LoongArch64: add new reloc types and
NT_LOONGARCH_HW_* into elf.h (Rich Felker <dalias@...c.org>)
- 2025/06/18 #2:
Re: [PATCH] time.h: drop non-standard and out-of-date CLOCK_SGI_CYCLE (Yao Zi <ziyao@...root.org>)
- 2025/06/18 #1:
Re: [PATCH] LoongArch64: add new reloc types and
NT_LOONGARCH_HW_* into elf.h (Yao Zi <ziyao@...root.org>)
- 2025/06/17 #9:
Re: Re: BUG: realloc(p,0) should be consistent with malloc(0) (Alejandro Colomar <alx@...nel.org>)
- 2025/06/17 #8:
Re[2]: Re: BUG: realloc(p,0) should be consistent with malloc(0) ("Laurent Bercot" <ska-dietlibc@...rnet.org>)
- 2025/06/17 #7:
Re[2]: Re: BUG: realloc(p,0) should be consistent with malloc(0) ("Laurent Bercot" <ska-dietlibc@...rnet.org>)
- 2025/06/17 #6:
Re: Re: BUG: realloc(p,0) should be consistent with malloc(0) (Rich Felker <dalias@...c.org>)
- 2025/06/17 #5:
Re: Re: BUG: realloc(p,0) should be consistent with malloc(0) (enh <enh@...gle.com>)
- 2025/06/17 #4:
Re: Re: BUG: realloc(p,0) should be consistent with malloc(0) (Paul Eggert <eggert@...ucla.edu>)
- 2025/06/17 #3:
Re: Re: BUG: realloc(p,0) should be consistent with malloc(0) (Rich Felker <dalias@...c.org>)
- 2025/06/17 #2:
Re: BUG: realloc(p,0) should be consistent with malloc(0) (Florian Weimer <fweimer@...hat.com>)
- 2025/06/17 #1:
Re: BUG: realloc(p,0) should be consistent with malloc(0) (enh <enh@...gle.com>)
- 2025/06/16 #13:
Re: BUG: realloc(p,0) should be consistent with malloc(0) (Joseph Myers <josmyers@...hat.com>)
- 2025/06/16 #12:
Re: BUG: realloc(p,0) should be consistent with malloc(0) (Alejandro Colomar <alx@...nel.org>)
- 2025/06/16 #11:
Re: BUG: realloc(p,0) should be consistent with malloc(0) (Alejandro Colomar <alx@...nel.org>)
- 2025/06/16 #10:
Re: BUG: realloc(p,0) should be consistent with malloc(0) (Alejandro Colomar <alx@...nel.org>)
- 2025/06/16 #9:
Re: BUG: realloc(p,0) should be consistent with malloc(0) (Alejandro Colomar <alx@...nel.org>)
- 2025/06/16 #8:
Re: BUG: realloc(p,0) should be consistent with malloc(0) (Adhemerval Zanella Netto <adhemerval.zanella@...aro.org>)
- 2025/06/16 #7:
Re: BUG: realloc(p,0) should be consistent with malloc(0) (Florian Weimer <fweimer@...hat.com>)
- 2025/06/16 #6:
Re: BUG: realloc(p,0) should be consistent with malloc(0) (Adhemerval Zanella Netto <adhemerval.zanella@...aro.org>)
- 2025/06/16 #5:
Re: BUG: realloc(p,0) should be consistent with malloc(0) (Paul Eggert <eggert@...ucla.edu>)
- 2025/06/16 #4:
Re: BUG: realloc(p,0) should be consistent with malloc(0) (enh <enh@...gle.com>)
- 2025/06/16 #3:
Re: BUG: realloc(p,0) should be consistent with malloc(0) (Alejandro Colomar <alx@...nel.org>)
- 2025/06/16 #2:
Re: BUG: realloc(p,0) should be consistent with malloc(0) (Rich Felker <dalias@...c.org>)
- 2025/06/16 #1:
BUG: realloc(p,0) should be consistent with malloc(0) (Alejandro Colomar <alx@...nel.org>)
- 2025/06/15 #2:
Re: On current (and future) use of LCTRANS (Rich Felker <dalias@...c.org>)
22120 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.