From: "Sivanupandi, Pitchumani" <Pitchumani.Sivanupandi@atmel.com>
To: "Sivanupandi, Pitchumani" <Pitchumani.Sivanupandi@atmel.com>,
"Georg-Johann Lay" <avr@gjlay.de>,
Denis Chertykov <chertykov@gmail.com>
Cc: GCC Patches <gcc-patches@gcc.gnu.org>,
Joerg Wunsch <joerg_wunsch@uriah.heep.sax.de>,
"Selvaraj, Senthil_Kumar" <Senthil_Kumar.Selvaraj@atmel.com>
Subject: RE: [patch,avr]: Part2: Fix various problems with specs and specs file generation.
Date: Wed, 15 Apr 2015 10:17:00 -0000 [thread overview]
Message-ID: <CAC140656783604CABA6AE60C2A6D5A49855E892@penmbx02.corp.atmel.com> (raw)
In-Reply-To: <CAC140656783604CABA6AE60C2A6D5A49855BB81@penmbx02.corp.atmel.com>
[-- Attachment #1: Type: text/plain, Size: 1232 bytes --]
> -----Original Message-----
> From: gcc-patches-owner@gcc.gnu.org [mailto:gcc-patches-
> owner@gcc.gnu.org] On Behalf Of Sivanupandi, Pitchumani
> Sent: Thursday, April 09, 2015 6:26 PM
> To: Georg-Johann Lay; Denis Chertykov
> Cc: GCC Patches; Joerg Wunsch; Selvaraj, Senthil_Kumar
> Subject: RE: [patch,avr]: Part2: Fix various problems with specs and specs
> file generation.
...
> >
> > If the device libs are moved, all the ~200 .dev/<device> directories
> > will contain just 1 file each: crt1.o. Is it much work to tidy that
> > up? (For example by renaming to, say, crt<device>.o and moving
> them
> > to a common place or to their natural multilib location.)
>
> No, It is possible to do with the same patch.
> I'll rename crt1.o to crt<device>.o and move it to multilib location.
Hi Johann,
This is done.
https://savannah.nongnu.org/bugs/?44574
Attached a patch for corresponding changes in gcc.
gcc/ChangeLog
* config/avr/avr-mcus.def: Change startup and device lib name
to crt<device>.o and lib<device>.a respectively.
* config/avr/avr.opt: Update device lib name.
* config/avr/gen-avr-mmcu-specs.c (print_mcu): Update start file name
and device lib name.
Regards,
Pitchumani
[-- Attachment #2: Change-crt-device-lib-name.patch --]
[-- Type: application/octet-stream, Size: 1868 bytes --]
diff --git a/gcc/config/avr/avr-mcus.def b/gcc/config/avr/avr-mcus.def
index ce4b782..8526578 100644
--- a/gcc/config/avr/avr-mcus.def
+++ b/gcc/config/avr/avr-mcus.def
@@ -44,8 +44,8 @@
used by DRIVER_SELF_SPECS and gen-avr-mmcu-specs.c for
- the name of the device specific specs file
in -specs=device-specs/spec-<NAME>
- - the name of the startup file dev/<NAME>/crt1.o
- - the name of the device library dev/<NAME>/libdev.a
+ - the name of the startup file crt<NAME>.o
+ - the name of the device library lib<NAME>.a
ARCH Specifies the multilib variant together with AVR_SHORT_SP
diff --git a/gcc/config/avr/avr.opt b/gcc/config/avr/avr.opt
index 5de5f90..1986c4f 100644
--- a/gcc/config/avr/avr.opt
+++ b/gcc/config/avr/avr.opt
@@ -97,4 +97,4 @@ Allow to use truncation instead of rounding towards 0 for fractional int types
nodevicelib
Driver Target Report RejectNegative
-Do not link against the device-specific library libdev.a
+Do not link against the device-specific library lib<device>.a
diff --git a/gcc/config/avr/gen-avr-mmcu-specs.c b/gcc/config/avr/gen-avr-mmcu-specs.c
index 3594d8a..0931920 100644
--- a/gcc/config/avr/gen-avr-mmcu-specs.c
+++ b/gcc/config/avr/gen-avr-mmcu-specs.c
@@ -171,11 +171,11 @@ print_mcu (const avr_mcu_t *mcu)
if (is_device)
{
fprintf (f, "*avrlibc_startfile:\n");
- fprintf (f, "\tdev/%s/crt1.o%%s", mcu->name);
+ fprintf (f, "\tcrt%s.o%%s", mcu->name);
fprintf (f, "\n\n");
fprintf (f, "*avrlibc_devicelib:\n");
- fprintf (f, "\t%%{!nodevicelib:dev/%s/libdev.a%%s}", mcu->name);
+ fprintf (f, "\t%%{!nodevicelib:lib%s.a%%s}", mcu->name);
fprintf (f, "\n\n");
}
#endif // WITH_AVRLIBC
next prev parent reply other threads:[~2015-04-15 10:17 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-03-02 19:40 [patch,avr]: " Georg-Johann Lay
2015-03-03 7:46 ` Denis Chertykov
2015-03-03 13:20 ` Senthil Kumar Selvaraj
2015-03-09 16:03 ` [patch,avr]: Part2: " Georg-Johann Lay
2015-03-09 20:00 ` Denis Chertykov
2015-03-10 15:02 ` [patch,avr]: Part3 and 4: " Georg-Johann Lay
2015-03-11 18:18 ` Denis Chertykov
2015-03-16 18:18 ` [patch,avr]: Part5: " Georg-Johann Lay
2015-03-17 6:37 ` Denis Chertykov
2015-04-06 9:54 ` [patch,avr]: Part2: " Sivanupandi, Pitchumani
2015-04-07 12:34 ` Georg-Johann Lay
2015-04-08 8:28 ` Denis Chertykov
2015-04-08 11:25 ` Georg-Johann Lay
2015-04-09 10:59 ` Sivanupandi, Pitchumani
2015-04-09 11:23 ` Georg-Johann Lay
2015-04-09 12:55 ` Sivanupandi, Pitchumani
2015-04-15 10:17 ` Sivanupandi, Pitchumani [this message]
2015-04-17 14:03 ` [patch,avr,installed] ad PR65296: Adjust specs to new avr-libc layout as of #44574 Georg-Johann Lay
2015-04-17 14:43 ` Denis Chertykov
2015-04-17 15:32 ` Georg-Johann Lay
2015-04-17 16:46 ` Denis Chertykov
2015-04-09 11:44 ` [patch,avr,committed]: ad PR65296: work around device-specs file + dejagnu for c++ Georg-Johann Lay
2015-03-09 16:21 ` [patch,avr]: Fix various problems with specs and specs file generation Georg-Johann Lay
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=CAC140656783604CABA6AE60C2A6D5A49855E892@penmbx02.corp.atmel.com \
--to=pitchumani.sivanupandi@atmel.com \
--cc=Senthil_Kumar.Selvaraj@atmel.com \
--cc=avr@gjlay.de \
--cc=chertykov@gmail.com \
--cc=gcc-patches@gcc.gnu.org \
--cc=joerg_wunsch@uriah.heep.sax.de \
/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).