public inbox for libc-alpha@sourceware.org
 help / color / mirror / Atom feed
From: Frank Scheiner <frank.scheiner@web.de>
To: Adhemerval Zanella <adhemerval.zanella@linaro.org>
Cc: libc-alpha@sourceware.org, "Tomáš Glozar" <tglozar@gmail.com>
Subject: Re: [PATCH] Remove ia64-linux-gnu
Date: Sat, 4 Nov 2023 20:59:41 +0100	[thread overview]
Message-ID: <fbdeb854-ca42-4835-8cdc-fb130ea2b747@web.de> (raw)
In-Reply-To: <20231104190225.2060378-1-adhemerval.zanella@linaro.org>

Dear Adhemerval, all,

On 04.11.23 20:02, Adhemerval Zanella wrote:
> Linux 6.7 removed ia64 from the official tree [1], following the general
> principle that a glibc port needs upstream support for the architecture
> in all the components it depends on (binutils, GCC, and the Linux
> kernel).

> Apart from the removal of sysdeps/ia64 and
> sysdeps/unix/sysv/linux/ia64, there are updates to various comments
> referencing ia64 for which removal of those references seemed
> appropriate. The configuration is removed from README and
> build-many-glibcs.py.

> The CONTRIBUTED-BY, elf/elf.h, manual/contrib.texi
> (the porting mention), *.po files, config.guess, and longlong.h are not
> changed.

> For Linux it allows cleanup some clone2 support on multiple
> files.
> The following bug can be closed as WONTFIX: BZ 22634 [2], BZ
> 14250 [3], BZ 21634 [4], BZ 10163 [5], BZ 16401 [6], and BZ 11585 [7].

> [1] >
https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=43ff221426d33db909f7159fdf620c3b052e2d1c
> [2] https://sourceware.org/bugzilla/show_bug.cgi?id=22634
> [3] https://sourceware.org/bugzilla/show_bug.cgi?id=14250
> [4] https://sourceware.org/bugzilla/show_bug.cgi?id=21634
> [5] https://sourceware.org/bugzilla/show_bug.cgi?id=10163
> [6] https://sourceware.org/bugzilla/show_bug.cgi?id=16401
> [7] https://sourceware.org/bugzilla/show_bug.cgi?id=11585

The speed this happens really surprises me and I hope there is no need
to rush with this removal, I would like to comment on your points in [8]
but need some more time for further research into this matter to get a
better picture of how much work ia64 is in the glibc.

[8]: https://sourceware.org/pipermail/libc-alpha/2023-November/152497.html

Only so much now, we would like to maintain Linux/ia64 (there is the
possibility that this returns to the kernel in a year's time, see [9])
and we also - as you already found out - started to work on the math
issues for ia64 in the glibc. We started this roughly just a month ago
and together with Aurelien's patch could make about 80 tests pass (30
FAIL => PASS, 50 UNSUPPORTED => PASS). That is not a very big thing, but
compared to what happened in this regard in the last ten years, it's not
bad I'd say, for a month's time.

[9]:
https://lore.kernel.org/linux-ia64/CAHk-=whFLZ67ffzt1juryCYcYz6eL_XjQF8WucDzwUR5H65+rA@mail.gmail.com/

Cheers,
Frank

  reply	other threads:[~2023-11-04 19:59 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-11-04 19:02 Adhemerval Zanella
2023-11-04 19:59 ` Frank Scheiner [this message]
2023-11-04 20:14   ` Sam James
2023-11-04 21:44     ` Florian Weimer
2023-11-06 12:29       ` Adhemerval Zanella Netto
2023-11-06 15:04       ` Carlos O'Donell
2023-11-06 16:28         ` Florian Weimer
2023-11-06 16:54           ` Adhemerval Zanella Netto
2023-11-06 16:33         ` Sam James
2023-11-06 11:48   ` Adhemerval Zanella Netto
2023-11-06 15:48 ` Carlos O'Donell

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=fbdeb854-ca42-4835-8cdc-fb130ea2b747@web.de \
    --to=frank.scheiner@web.de \
    --cc=adhemerval.zanella@linaro.org \
    --cc=libc-alpha@sourceware.org \
    --cc=tglozar@gmail.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
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).