public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "gjl at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug target/65296] [avr] fix various issues with specs file generation
Date: Tue, 17 Mar 2015 10:34:00 -0000 [thread overview]
Message-ID: <bug-65296-4-ckfSEaSatn@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-65296-4@http.gcc.gnu.org/bugzilla/>
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=65296
--- Comment #6 from Georg-Johann Lay <gjl at gcc dot gnu.org> ---
Author: gjl
Date: Tue Mar 17 10:34:11 2015
New Revision: 221475
URL: https://gcc.gnu.org/viewcvs?rev=221475&root=gcc&view=rev
Log:
PR target/65296
* config/avr/avr.opt (-nodevicelib): New option.
* doc/invoke.texi (AVR Options): Document it.
* config/avr/avrlibc.h (LIB_SPEC, LIBGCC_SPEC) [avr1]: Don't link
libgcc.a, libc.a, libm.a.
* config/avr/specs.h: Same.
* config/avr/gen-avr-mmcu-specs.c (print_mcu): Don't print specs
which don't (directly) depend on the device. Print more help.
(*avrlibc_devicelib) [-nodevicelib]: Don't link libdev.a.
(*cpp): Don't define __AVR_DEV_LIB_NAME__.
* config/avr/driver-avr.c: Remove -nodevicelib from option list in
case of an error.
(avr_devicespecs_file): Use suffix "%s" instead of absolute path
for specs file name.
* config/avr/avr-arch.h (avr_mcu_t) [.library_name]: Remove.
* config/avr/avr-mcus.def: Adjust initializers and comments.
Modified:
trunk/gcc/ChangeLog
trunk/gcc/config/avr/avr-arch.h
trunk/gcc/config/avr/avr-devices.c
trunk/gcc/config/avr/avr-mcus.def
trunk/gcc/config/avr/avr.opt
trunk/gcc/config/avr/avrlibc.h
trunk/gcc/config/avr/driver-avr.c
trunk/gcc/config/avr/gen-avr-mmcu-specs.c
trunk/gcc/config/avr/specs.h
trunk/gcc/doc/invoke.texi
next prev parent reply other threads:[~2015-03-17 10:34 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-03-03 11:00 [Bug target/65296] New: " gjl at gcc dot gnu.org
2015-03-03 11:03 ` [Bug target/65296] " gjl at gcc dot gnu.org
2015-03-03 11:31 ` gjl at gcc dot gnu.org
2015-03-10 9:51 ` gjl at gcc dot gnu.org
2015-03-11 18:36 ` gjl at gcc dot gnu.org
2015-03-11 18:51 ` gjl at gcc dot gnu.org
2015-03-17 10:34 ` gjl at gcc dot gnu.org [this message]
2015-03-23 19:33 ` gjl at gcc dot gnu.org
2015-04-09 11:37 ` gjl at gcc dot gnu.org
2015-04-17 13:54 ` gjl at gcc dot gnu.org
2015-04-23 17:08 ` gjl at gcc dot gnu.org
2015-04-27 11:43 ` gjl at gcc dot gnu.org
2015-04-27 11:50 ` gjl at gcc dot gnu.org
2015-04-27 11:53 ` 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-65296-4-ckfSEaSatn@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).