public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "giulio.benetti at benettiengineering dot com" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c/102472] New: Infinite loop on m68k
Date: Thu, 23 Sep 2021 16:26:24 +0000	[thread overview]
Message-ID: <bug-102472-4@http.gcc.gnu.org/bugzilla/> (raw)

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

            Bug ID: 102472
           Summary: Infinite loop on m68k
           Product: gcc
           Version: 11.2.0
            Status: UNCONFIRMED
          Severity: normal
          Priority: P3
         Component: c
          Assignee: unassigned at gcc dot gnu.org
          Reporter: giulio.benetti at benettiengineering dot com
  Target Milestone: ---

When building python-uvloop package on Buildroot for m68k gcc enters an
infinite loop on:
'''
/home/giuliobenetti/autobuild/run/instance-3/output-1/host/bin/m68k-linux-gcc
-Wno-unused-result -Wsign-compare -DNDEBUG -g -fwrapv -O3 -Wall
-D_LARGEFILE_SOURCE -D_LARGEFILE64_SOURCE -D_FILE_OFFSET_BITS=64 -Os -g2
-D_LARGEFILE_SOURCE -D_LARGEFILE64_SOURCE -D_FILE_OFFSET_BITS=64 -Os -g2
-D_LARGEFILE_SOURCE -D_LARGEFILE64_SOURCE -D_FILE_OFFSET_BITS=64 -fPIC
-I/home/giuliobenetti/autobuild/run/instance-3/output-1/host/m68k-buildroot-linux-uclibc/sysroot/usr/include/python3.9
-c uvloop/loop.c -o build/temp.linux-x86_64-3.9/uvloop/loop.o -O2
'''

To reproduce it:

# git clone git://git.busybox.net/buildroot
# wget https://git.busybox.net/buildroot-test/tree/utils/br-reproduce-build

- modify BASE_GIT=... with your buildroot path in br-reproduce-build then:
# chmod a+x br-reproduce-build
# ./br-reproduce-build 17d6e6422abadcd6313c430c40f2a5d7162dbbd3

The only way I've found to build correctly is to turn off optimization
overriding CFLAGS with -O0.

In this case that we have an infinite loop, I don't know how provide .i and .s
files. Can you please point me some instruction for this case?

Thanks in advance

             reply	other threads:[~2021-09-23 16:26 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-09-23 16:26 giulio.benetti at benettiengineering dot com [this message]
2021-09-23 19:25 ` [Bug target/102472] " pinskia at gcc dot gnu.org
2021-09-23 20:01 ` giulio.benetti at benettiengineering dot com
2021-09-23 20:03 ` giulio.benetti at benettiengineering dot com
2021-09-23 20:03 ` giulio.benetti at benettiengineering dot com
2021-09-23 23:51 ` pinskia at gcc dot gnu.org
2021-09-24  7:04 ` rguenth at gcc dot gnu.org
2021-09-24 21:20 ` giulio.benetti at benettiengineering dot com

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-102472-4@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).