public inbox for gcc-patches@gcc.gnu.org
 help / color / mirror / Atom feed
From: Andreas Schwab <schwab@linux-m68k.org>
To: Segher Boessenkool <segher@kernel.crashing.org>
Cc: Adhemerval Zanella Netto <adhemerval.zanella@linaro.org>,
	joseph_myers@mentor.com,
	 Richard Biener <richard.guenther@gmail.com>,
	gcc-patches@gcc.gnu.org
Subject: Re: [PATCH] longlong.h: Do no use asm input cast for clang
Date: Tue, 10 Jan 2023 15:35:37 +0100	[thread overview]
Message-ID: <875ydebgp2.fsf@igel.home> (raw)
In-Reply-To: <20230110132003.GQ25951@gate.crashing.org> (Segher Boessenkool's message of "Tue, 10 Jan 2023 07:20:03 -0600")

On Jan 10 2023, Segher Boessenkool wrote:

> The file starts with
>
> /* longlong.h -- definitions for mixed size 32/64 bit arithmetic.
>    Copyright (C) 1991-2022 Free Software Foundation, Inc.
>
>    This file is part of the GNU C Library.
>
> Please change that first then?

GCC is the source of the original version of longlong.h (from 1991).  It
has then been imported into GMP, from where it found its way into GLIBC.
After that, the file has been synchronized back and forth between GCC
and GLIBC.

-- 
Andreas Schwab, schwab@linux-m68k.org
GPG Key fingerprint = 7578 EB47 D4E5 4D69 2510  2552 DF73 E780 A9DA AEC1
"And now for something completely different."

  reply	other threads:[~2023-01-10 14:35 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-11-30 18:16 Adhemerval Zanella
2022-11-30 23:24 ` Segher Boessenkool
2022-12-01  7:26   ` Richard Biener
2022-12-12 18:15     ` Segher Boessenkool
2022-12-12 17:10   ` Adhemerval Zanella Netto
2022-12-12 23:52     ` Segher Boessenkool
2023-01-10 12:26       ` Adhemerval Zanella Netto
2023-01-10 13:20         ` Segher Boessenkool
2023-01-10 14:35           ` Andreas Schwab [this message]
2023-01-10 18:20             ` Segher Boessenkool
2023-01-10 20:33         ` Joseph Myers

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=875ydebgp2.fsf@igel.home \
    --to=schwab@linux-m68k.org \
    --cc=adhemerval.zanella@linaro.org \
    --cc=gcc-patches@gcc.gnu.org \
    --cc=joseph_myers@mentor.com \
    --cc=richard.guenther@gmail.com \
    --cc=segher@kernel.crashing.org \
    /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).