public inbox for gcc-patches@gcc.gnu.org
 help / color / mirror / Atom feed
From: Joel Sherrill <joel.sherrill@oarcorp.com>
To: Jeff Law <law@redhat.com>,Jan Sommer
	<soja-lists@aries.uberspace.de>,"gcc-patches@gcc.gnu.org"
	<gcc-patches@gcc.gnu.org>
Cc: "devel@rtems.org"
	<devel@rtems.org>,"sebastian.huber@embedded-brains.de"
	<sebastian.huber@embedded-brains.de>
Subject: Re: [PATCH] Fix declaration of pthread-structs in s-osinte-rtems.ads (ada/68169)
Date: Wed, 02 Dec 2015 17:34:00 -0000	[thread overview]
Message-ID: <DAA451A1-B5FC-4368-B977-ABCA5E1A427D@oarcorp.com> (raw)
In-Reply-To: <565E9A4E.6070101@redhat.com>



On December 2, 2015 2:14:22 AM EST, Jeff Law <law@redhat.com> wrote:
>On 12/01/2015 12:56 PM, Jan Sommer wrote:
>> Am Monday 30 November 2015, 16:19:30 schrieb Jeff Law:
>>> On 11/30/2015 03:06 PM, Jan Sommer wrote:
>>>> Could someone with write access please commit the patch?
>>>> The paperwork with the FSF has gone through. If something else is
>missing, please tell me.
>>>> I won't be available next week.
>>> I'm not sure what you built your patches again, but I can't apply
>them
>>> to the trunk.  Can you resend a patch as a diff against the trunk.
>>>
>>> Often I can fix things by hand, but this is Ada and I'd be much more
>>> likely to botch something.
>>
>> I updated the patches again. They should now fit with the heads of
>the respective branches again.
>> Maybe the Changelog will be out of synch again.
>> The patches are for the following branches:
>> ada-68169_4.9.diff   -->  gcc-4_9-branch
>> ada-68169_5.x.diff  -->   gcc-5-branch
>> ada-68169_trunk.diff --> trunk
>>
>> Let me know if they apply this time. I used svn diff to create them
>and used patch -p0 to test if they apply locally.
>THanks.  I've committed this to the trunk based on Joel's comments.
>
>The gcc-5 branch is frozen for the upcoming release and gcc-4.9 is 
>regression/doc fixes only.  It'll be up to the release managers whether
>
>or not to backport to those branches.

Thanks Jeff. 

I would consider this a regression. RTEMS changed the pthread_attr_t when we added thread affinity and updating Ada to match slipped through. We knew it needed attention for SMP but missed this critical piece to keep it working.

Jan.. Is there a gcc PR for this? To get it on a release branch, it is better to have one.

>Thanks.
>
>Jeff

--joel

  reply	other threads:[~2015-12-02 17:34 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-11-23 22:21 Jan Sommer
     [not found] ` <5654078A.5010807@embedded-brains.de>
     [not found]   ` <3389407.csH2gdyrKe@kubuntu>
2015-11-30 22:22     ` Jan Sommer
2015-11-30 23:20       ` Jeff Law
2015-12-01 19:57         ` Jan Sommer
2015-12-02  7:14           ` Jeff Law
2015-12-02 17:34             ` Joel Sherrill [this message]
2015-12-02 22:23               ` Jan Sommer
2015-12-04 18:45                 ` Jeff Law
2015-12-04 18:49                   ` Joel Sherrill
  -- strict thread matches above, loose matches on Subject: below --
2015-11-18 20:50 Jan Sommer

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=DAA451A1-B5FC-4368-B977-ABCA5E1A427D@oarcorp.com \
    --to=joel.sherrill@oarcorp.com \
    --cc=devel@rtems.org \
    --cc=gcc-patches@gcc.gnu.org \
    --cc=law@redhat.com \
    --cc=sebastian.huber@embedded-brains.de \
    --cc=soja-lists@aries.uberspace.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).