All of lore.kernel.org
 help / color / mirror / Atom feed
From: Petr Vorel <pvorel@suse.cz>
To: ltp@lists.linux.it
Subject: [LTP] [PATCH] Fix the 64-bit macro definition of mips architecture
Date: Mon, 26 Apr 2021 15:09:21 +0200	[thread overview]
Message-ID: <YIa7gZn/5i9pBqXf@pevik> (raw)
In-Reply-To: <20210426070320.iow3avu2pq22qled@vireshk-i7>

> On 26-04-21, 15:00, sujiaxun wrote:
> > uos@uos-PC:~$ echo |gcc -dM -E - | grep -i arch
> > #define _MIPS_ARCH "mips64r2"
> > #define _MIPS_ARCH_MIPS64R2 1
> > uos@uos-PC:~$ echo |gcc -dM -E - | grep -i mips64
> > #define _MIPS_ISA _MIPS_ISA_MIPS64
> > #define _MIPS_TUNE "mips64r2"
> > #define _MIPS_TUNE_MIPS64R2 1
> > #define _MIPS_ARCH "mips64r2"
> > #define _MIPS_ARCH_MIPS64R2 1
> > #define __mips64 1
> > uos@uos-PC:~$ uname  -m
> > mips64
Thanks for verification!

> > The mips architecture gcc has no built-in __arch64__, only __mips64
> > definitions. Of course, "__BITS_PER_LONG == 64" can also be used, but I
> > think it is better to use __mips64 in the mips architecture.

> Hmm, I will rather try to do what the kernel source code does, i.e.
> use __BITS_PER_LONG here instead.
+1

Kind regards,
Petr

  parent reply	other threads:[~2021-04-26 13:09 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-04-22  7:26 [LTP] [PATCH] Fix the 64-bit macro definition of mips architecture sujiaxun
2021-04-26  5:42 ` Petr Vorel
2021-04-26  5:55   ` Viresh Kumar
2021-04-26  6:17     ` Petr Vorel
2021-04-26  6:23       ` Viresh Kumar
2021-04-26  7:00         ` sujiaxun
2021-04-26  7:03           ` Viresh Kumar
2021-04-26  7:53             ` sujiaxun
2021-04-26  8:12               ` Viresh Kumar
2021-04-26  8:28                 ` sujiaxun
2021-04-26  8:44                   ` Viresh Kumar
2021-04-26 13:09             ` Petr Vorel [this message]
  -- strict thread matches above, loose matches on Subject: below --
2021-04-26  7:48 sujiaxun
2021-04-26  9:00 ` sujiaxun
2021-04-26  9:02   ` Viresh Kumar
2021-04-27 12:32 ` Petr Vorel

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=YIa7gZn/5i9pBqXf@pevik \
    --to=pvorel@suse.cz \
    --cc=ltp@lists.linux.it \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.