public inbox for gcc-patches@gcc.gnu.org
 help / color / mirror / Atom feed
From: Jerry DeLisle <jvdelisle@charter.net>
To: Janne Blomqvist <blomqvist.janne@gmail.com>,
	fortran@gcc.gnu.org, gcc-patches@gcc.gnu.org
Subject: Re: [PATCH] Use __BYTE_ORDER__ predefined macro instead of runtime check
Date: Wed, 22 Nov 2017 16:57:00 -0000	[thread overview]
Message-ID: <4a7c2772-1924-a028-d431-adf875e12db9@charter.net> (raw)
In-Reply-To: <1511354047-32527-1-git-send-email-blomqvist.janne@gmail.com>

On 11/22/2017 04:34 AM, Janne Blomqvist wrote:
> By using the __BYTE_ORDER__ predefined macro we don't need the
> determine_endianness function anymore.
> 
> Regtested on x86_64-pc-linux-gnu, Ok for trunk?
> 

Looks good, thanks for patch!

Jerry

  reply	other threads:[~2017-11-22 16:49 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-11-22 12:59 Janne Blomqvist
2017-11-22 16:57 ` Jerry DeLisle [this message]
2017-11-22 18:42 ` Thomas Koenig
2017-11-22 19:22   ` Andreas Schwab
2017-11-22 20:03   ` Janne Blomqvist

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=4a7c2772-1924-a028-d431-adf875e12db9@charter.net \
    --to=jvdelisle@charter.net \
    --cc=blomqvist.janne@gmail.com \
    --cc=fortran@gcc.gnu.org \
    --cc=gcc-patches@gcc.gnu.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).