public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "jamesgua at ca dot ibm.com" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c/98209] New: printf failed with O1 or above
Date: Tue, 08 Dec 2020 21:35:59 +0000	[thread overview]
Message-ID: <bug-98209-4@http.gcc.gnu.org/bugzilla/> (raw)

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

            Bug ID: 98209
           Summary: printf failed with O1 or above
           Product: gcc
           Version: 9.3.0
            Status: UNCONFIRMED
          Severity: normal
          Priority: P3
         Component: c
          Assignee: unassigned at gcc dot gnu.org
          Reporter: jamesgua at ca dot ibm.com
  Target Milestone: ---

Testing file:

#include <stdio.h>

int main(int argc, char** argv) __attribute__ ((__target__ ("no-sse,no-mmx"))); 
int main(int argc, char** argv)
{
        printf("hello!\n");
        return 0;
} 

cmd to compile: gcc -O3 -c test.c
On Ubuntu 20.04 (gcc version 9.3.0 (Ubuntu 9.3.0-17ubuntu1~20.04)) it failed
with "inlining failed in call to always_inline printf’: target specific option
mismatch" but it works on Ubuntu 16.04 (gcc version 5.4.0 20160609 (Ubuntu
5.4.0-6ubuntu1~16.04.12))

If not supported pls let me know.

             reply	other threads:[~2020-12-08 21:35 UTC|newest]

Thread overview: 23+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-12-08 21:35 jamesgua at ca dot ibm.com [this message]
2020-12-09  0:00 ` [Bug c/98209] " pinskia at gcc dot gnu.org
2020-12-09  1:27 ` jamesgua at ca dot ibm.com
2020-12-09  8:24 ` marxin at gcc dot gnu.org
2020-12-09  9:03 ` rguenth at gcc dot gnu.org
2020-12-09  9:05 ` [Bug middle-end/98209] [8/9/10/11 Regression] " rguenth at gcc dot gnu.org
2020-12-09  9:05 ` rguenth at gcc dot gnu.org
2020-12-09  9:08 ` marxin at gcc dot gnu.org
2020-12-09  9:18 ` rguenther at suse dot de
2020-12-09 15:04 ` jamesgua at ca dot ibm.com
2021-01-14 11:03 ` rguenth at gcc dot gnu.org
2021-01-28 18:02 ` jakub at gcc dot gnu.org
2021-01-29  7:34 ` rguenther at suse dot de
2021-01-29  8:55 ` jakub at gcc dot gnu.org
2021-03-25 12:37 ` cvs-commit at gcc dot gnu.org
2021-03-25 12:42 ` hjl.tools at gmail dot com
2021-03-25 12:54 ` [Bug middle-end/98209] [8/9/10 " rguenth at gcc dot gnu.org
2021-03-25 13:59 ` hjl.tools at gmail dot com
2021-05-14  9:54 ` [Bug middle-end/98209] [9/10 " jakub at gcc dot gnu.org
2021-06-01  8:19 ` rguenth at gcc dot gnu.org
2022-05-27  9:44 ` [Bug middle-end/98209] [10 " rguenth at gcc dot gnu.org
2022-06-28 10:42 ` jakub at gcc dot gnu.org
2023-07-07  9:18 ` [Bug middle-end/98209] [11/12/13/14 " rguenth 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-98209-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).