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/107201] [avr] -nodevicelib not working for devices -mmcu=avr... Date: Tue, 16 Jan 2024 08:16:49 +0000 [thread overview] Message-ID: <bug-107201-4-zOXxNuVaDj@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-107201-4@http.gcc.gnu.org/bugzilla/> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=107201 --- Comment #4 from GCC Commits <cvs-commit at gcc dot gnu.org> --- The releases/gcc-12 branch has been updated by Georg-Johann Lay <gjl@gcc.gnu.org>: https://gcc.gnu.org/g:ebdc3aae0a4705d0b72b69a37fdafa5613343d5d commit r12-10100-gebdc3aae0a4705d0b72b69a37fdafa5613343d5d Author: Georg-Johann Lay <avr@gjlay.de> Date: Mon Jan 15 13:25:59 2024 +0100 AVR: target/107201: Make -nodevicelib work for all devices. driver-avr.cc contains a spec that discriminates between cores and devices by means of a mmcu=avr* spec pattern. This does not work for new devices like AVR128* which also start with mmcu=avr like all cores do. The patch uses a new spec function in order to tell apart cores from devices. gcc/ PR target/107201 * config/avr/avr.h (EXTRA_SPEC_FUNCTIONS): Add no-devlib, avr_no_devlib. * config/avr/driver-avr.cc (avr_no_devlib): New function. (avr_devicespecs_file): Use it to remove -nodevicelib from the options for cores only. * config/avr/avr-arch.h (avr_get_parch): New prototype. * config/avr/avr-devices.cc (avr_get_parch): New function. (cherry picked from commit 86fac7ee1688bdec245a43f6d2ab49fb238892e4)
next prev parent reply other threads:[~2024-01-16 8:16 UTC|newest] Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top 2022-10-10 14:37 [Bug target/107201] New: " gjl at gcc dot gnu.org 2022-10-11 17:25 ` [Bug target/107201] " gjl at gcc dot gnu.org 2024-01-15 15:17 ` cvs-commit at gcc dot gnu.org 2024-01-16 7:42 ` cvs-commit at gcc dot gnu.org 2024-01-16 8:16 ` cvs-commit at gcc dot gnu.org [this message] 2024-01-16 8:18 ` gjl at gcc dot gnu.org 2024-01-16 8:40 ` gjl 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-107201-4-zOXxNuVaDj@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).