public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "cvs-commit at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug target/104090] [10/11/12 Regression] powerpc: asm machine directive wrong for FSL processors Date: Thu, 03 Feb 2022 06:53:45 +0000 [thread overview] Message-ID: <bug-104090-4-QvW0je8s1I@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-104090-4@http.gcc.gnu.org/bugzilla/> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=104090 --- Comment #4 from CVS Commits <cvs-commit at gcc dot gnu.org> --- The releases/gcc-10 branch has been updated by Sebastian Huber <sh@gcc.gnu.org>: https://gcc.gnu.org/g:d568abb25fc799123168aac840372b28bb81f85d commit r10-10435-gd568abb25fc799123168aac840372b28bb81f85d Author: Sebastian Huber <sebastian.huber@embedded-brains.de> Date: Tue Jan 18 12:44:53 2022 +0100 powerpc: Fix asm machine directive for some CPUs For some CPUs, the assembler machine directive cannot be determined by ISA flags. gcc/ PR target/104090 * config/rs6000/rs6000.c (rs6000_machine_from_flags): Use also rs6000_cpu.
next prev parent reply other threads:[~2022-02-03 6:53 UTC|newest] Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top 2022-01-18 10:59 [Bug target/104090] New: " sebastian.huber@embedded-brains.de 2022-01-18 11:12 ` [Bug target/104090] " rguenth at gcc dot gnu.org 2022-01-18 11:14 ` sebastian.huber@embedded-brains.de 2022-01-19 6:51 ` cvs-commit at gcc dot gnu.org 2022-02-02 19:24 ` cvs-commit at gcc dot gnu.org 2022-02-03 6:53 ` cvs-commit at gcc dot gnu.org [this message] 2022-02-03 6:54 ` sebastian.huber@embedded-brains.de 2022-02-25 8:00 ` judge.packham at gmail 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-104090-4-QvW0je8s1I@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: linkBe 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).