public inbox for gcc-patches@gcc.gnu.org
 help / color / mirror / Atom feed
From: Denis Chertykov <chertykov@gmail.com>
To: Georg-Johann Lay <avr@gjlay.de>
Cc: "Sivanupandi, Pitchumani" <Pitchumani.Sivanupandi@atmel.com>,
	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,installed] ad PR65296: Adjust specs to new avr-libc layout as of #44574
Date: Fri, 17 Apr 2015 14:43:00 -0000	[thread overview]
Message-ID: <CADOs=zYj-dO7y6KuQKLH5KkG4ToRngt6ySDBSzvNZ0Dwq=yRnQ@mail.gmail.com> (raw)
In-Reply-To: <5531128C.3010709@gjlay.de>

2015-04-17 17:02 GMT+03:00 Georg-Johann Lay <avr@gjlay.de>:
> ...I went ahead and installed as
>
> http://gcc.gnu.org/r222179
>
> It will be backported to 5.2 as soon as 5.1 is open for patches again
> (assuming RM won't approve this one for 5.1).

IMHO AVR port is not locked for patches.
It's not a primary target.

>
>
> As far as I can tell, all works fine now, even with install-paths containing
> spaces and LTO.
>
>
> Johann
>
>
> 2015-04-17  Sivanupandi Pitchumani <Pitchumani.Sivanupandi@atmel.com>
>
>         PR target/65296
>         * config/avr/gen-avr-mmcu-specs.c (*avrlibc_startfile): Adjust
>         to new AVR-LibC file layout (bug #44574).
>         (*avrlibc_devicelib): Same.
>         * config/avr/avr-mcus.def: Adjust comments.
>         * config/avr/avr.opt (nodevicelib): Adjust help.
>
>
>
> Index: config/avr/gen-avr-mmcu-specs.c
> ===================================================================
> --- config/avr/gen-avr-mmcu-specs.c     (revision 222178)
> +++ config/avr/gen-avr-mmcu-specs.c     (revision 222179)
> @@ -171,11 +171,11 @@ bool is_arch = NULL == mcu->macro;
>    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:-l%s}", mcu->name);
>        fprintf (f, "\n\n");
>      }
>  #endif  // WITH_AVRLIBC
> Index: config/avr/avr-mcus.def
> ===================================================================
> --- config/avr/avr-mcus.def     (revision 222178)
> +++ config/avr/avr-mcus.def     (revision 222179)
> @@ -44,8 +44,8 @@ Before including this file, define a mac
>                       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
> +                     - to link the device library by means of -l<NAME>
>
>         ARCH          Specifies the multilib variant together with
> AVR_SHORT_SP
>
> Index: config/avr/avr.opt
> ===================================================================
> --- config/avr/avr.opt  (revision 222178)
> +++ config/avr/avr.opt  (revision 222179)
> @@ -97,4 +97,4 @@ Allow to use truncation instead of round
>
>  nodevicelib
>  Driver Target Report RejectNegative
> -Do not link against the device-specific library libdev.a
> +Do not link against the device-specific library lib<MCU>.a
>

  reply	other threads:[~2015-04-17 14:43 UTC|newest]

Thread overview: 23+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-03-02 19:40 [patch,avr]: Fix various problems with specs and specs file generation 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
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 [this message]
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='CADOs=zYj-dO7y6KuQKLH5KkG4ToRngt6ySDBSzvNZ0Dwq=yRnQ@mail.gmail.com' \
    --to=chertykov@gmail.com \
    --cc=Pitchumani.Sivanupandi@atmel.com \
    --cc=Senthil_Kumar.Selvaraj@atmel.com \
    --cc=avr@gjlay.de \
    --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).