public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "pinskia at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug middle-end/106642] cc1 compiler hangs when cross-compiling ring_buffer.c (from kernel/events) on Aarch64
Date: Tue, 16 Aug 2022 14:46:07 +0000	[thread overview]
Message-ID: <bug-106642-4-Y5jRrB1noV@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-106642-4@http.gcc.gnu.org/bugzilla/>

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=106642

--- Comment #5 from Andrew Pinski <pinskia at gcc dot gnu.org> ---

  max_order = ( __builtin_constant_p(nr_pages) ? (
__builtin_constant_p(nr_pages) ? ( (nr_pages) < 2 ? 0 : (nr_pages) & (1ULL <<
63) ? 63 : (nr_pages) & (1ULL << 62) ? 62 : (nr_pages) & (1ULL << 61) ? 61 :
(nr_pages) & (1ULL << 60) ? 60 : (nr_pages) & (1ULL << 59) ? 59 : (nr_pages) &
(1ULL << 58) ? 58 : (nr_pages) & (1ULL << 57) ? 57 : (nr_pages) & (1ULL << 56)
? 56 : (nr_pages) & (1ULL << 55) ? 55 : (nr_pages) & (1ULL << 54) ? 54 :
(nr_pages) & (1ULL << 53) ? 53 : (nr_pages) & (1ULL << 52) ? 52 : (nr_pages) &
(1ULL << 51) ? 51 : (nr_pages) & (1ULL << 50) ? 50 : (nr_pages) & (1ULL << 49)
? 49 : (nr_pages) & (1ULL << 48) ? 48 : (nr_pages) & (1ULL << 47) ? 47 :
(nr_pages) & (1ULL << 46) ? 46 : (nr_pages) & (1ULL << 45) ? 45 : (nr_pages) &
(1ULL << 44) ? 44 : (nr_pages) & (1ULL << 43) ? 43 : (nr_pages) & (1ULL << 42)
? 42 : (nr_pages) & (1ULL << 41) ? 41 : (nr_pages) & (1ULL << 40) ? 40 :
(nr_pages) & (1ULL << 39) ? 39 : (nr_pages) & (1ULL << 38) ? 38 : (nr_pages) &
(1ULL << 37) ? 37 : (nr_pages) & (1ULL << 36) ? 36 : (nr_pages) & (1ULL << 35)
? 35 : (nr_pages) & (1ULL << 34) ? 34 : (nr_pages) & (1ULL << 33) ? 33 :
(nr_pages) & (1ULL << 32) ? 32 : (nr_pages) & (1ULL << 31) ? 31 : (nr_pages) &
(1ULL << 30) ? 30 : (nr_pages) & (1ULL << 29) ? 29 : (nr_pages) & (1ULL << 28)
? 28 : (nr_pages) & (1ULL << 27) ? 27 : (nr_pages) & (1ULL << 26) ? 26 :
(nr_pages) & (1ULL << 25) ? 25 : (nr_pages) & (1ULL << 24) ? 24 : (nr_pages) &
(1ULL << 23) ? 23 : (nr_pages) & (1ULL << 22) ? 22 : (nr_pages) & (1ULL << 21)
? 21 : (nr_pages) & (1ULL << 20) ? 20 : (nr_pages) & (1ULL << 19) ? 19 :
(nr_pages) & (1ULL << 18) ? 18 : (nr_pages) & (1ULL << 17) ? 17 : (nr_pages) &
(1ULL << 16) ? 16 : (nr_pages) & (1ULL << 15) ? 15 : (nr_pages) & (1ULL << 14)
? 14 : (nr_pages) & (1ULL << 13) ? 13 : (nr_pages) & (1ULL << 12) ? 12 :
(nr_pages) & (1ULL << 11) ? 11 : (nr_pages) & (1ULL << 10) ? 10 : (nr_pages) &
(1ULL << 9) ? 9 : (nr_pages) & (1ULL << 8) ? 8 : (nr_pages) & (1ULL << 7) ? 7 :
(nr_pages) & (1ULL << 6) ? 6 : (nr_pages) & (1ULL << 5) ? 5 : (nr_pages) &
(1ULL << 4) ? 4 : (nr_pages) & (1ULL << 3) ? 3 : (nr_pages) & (1ULL << 2) ? 2 :
1) : -1) : (sizeof(nr_pages) <= 4) ? __ilog2_u32(nr_pages) :
__ilog2_u64(nr_pages) );

  parent reply	other threads:[~2022-08-16 14:46 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-08-16 13:29 [Bug c/106642] New: " pivanov at hotmail dot com
2022-08-16 13:31 ` [Bug c/106642] " pivanov at hotmail dot com
2022-08-16 13:56 ` [Bug middle-end/106642] " rearnsha at gcc dot gnu.org
2022-08-16 14:00 ` pinskia at gcc dot gnu.org
2022-08-16 14:09 ` pivanov at hotmail dot com
2022-08-16 14:46 ` pinskia at gcc dot gnu.org [this message]
2022-08-16 14:48 ` pinskia at gcc dot gnu.org

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=bug-106642-4-Y5jRrB1noV@http.gcc.gnu.org/bugzilla/ \
    --to=gcc-bugzilla@gcc.gnu.org \
    --cc=gcc-bugs@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).