public inbox for gcc-patches@gcc.gnu.org
 help / color / mirror / Atom feed
From: Christophe Lyon <christophe.lyon@linaro.org>
To: Maxim Ostapenko <m.ostapenko@partner.samsung.com>
Cc: Jakub Jelinek <jakub@redhat.com>,
	Kostya Serebryany <kcc@google.com>,
		GCC Patches <gcc-patches@gcc.gnu.org>,
	Yury Gribov <y.gribov@samsung.com>,
		Vyacheslav Barinov <v.barinov@samsung.com>,
	Slava Garbuzov <v.garbuzov@samsung.com>,
		Adhemerval Zanella <adhemerval.zanella@linaro.org>
Subject: Re: [PATCH 1/2] Libsanitizer merge from upstream r253555.
Date: Tue, 24 Nov 2015 09:24:00 -0000	[thread overview]
Message-ID: <CAKdteOb8+O=PpTDdX3tZqeAE_4ojO02dujm=PYxwXQqTnvrkBQ@mail.gmail.com> (raw)
In-Reply-To: <565426A4.1050804@partner.samsung.com>

On 24 November 2015 at 09:58, Maxim Ostapenko
<m.ostapenko@partner.samsung.com> wrote:
> On 24/11/15 11:38, Jakub Jelinek wrote:
>>
>> On Tue, Nov 24, 2015 at 11:36:20AM +0300, Maxim Ostapenko wrote:
>>>
>>> Ok, does it look better now?
>>
>> Sure, this is ok for trunk.
>>
>>> diff --git a/libsanitizer/ChangeLog b/libsanitizer/ChangeLog
>>> index b97fc7d..c392c57 100644
>>> --- a/libsanitizer/ChangeLog
>>> +++ b/libsanitizer/ChangeLog
>>> @@ -1,3 +1,7 @@
>>> +2015-11-24  Maxim Ostapenko  <m.ostapenko@partner.samsung.com>
>>> +
>>> +       * include/system/linux/asm/ptrace.h: New header.
>>> +
>>>   2015-11-23  Maxim Ostapenko  <m.ostapenko@partner.samsung.com>
>>>         * All source files: Merge from upstream r253555.
>>> diff --git a/libsanitizer/include/system/linux/asm/ptrace.h
>>> b/libsanitizer/include/system/linux/asm/ptrace.h
>>> new file mode 100644
>>> index 0000000..d4249fe
>>> --- /dev/null
>>> +++ b/libsanitizer/include/system/linux/asm/ptrace.h
>>> @@ -0,0 +1,7 @@
>>> +#include_next <linux/asm/ptrace.h>
>>> +/* ARM_VFPREGS_SIZE has been added in 3.0 */
>>> +#if defined(__arm__) && !defined(ARM_VFPREGS_SIZE)
>>> +/* The size of the user-visible VFP state as seen by
>>> PTRACE_GET/SETVFPREGS
>>> +   and core dumps.  */
>>> +#define ARM_VFPREGS_SIZE ( 32 * 8 /*fpregs*/ + 4 /*fpscr*/ )
>>> +#endif
>>
>>         Jakub
>>
>
> Thanks, applied as r230790.
>
> Christophe, please let me know if it cured your build.
>

Sure.
I had a build in progress with your proposed patch, but it didn't
complete before you committed :-)

> -Maxim

  reply	other threads:[~2015-11-24  9:21 UTC|newest]

Thread overview: 26+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-11-23  7:46 [PATCH 0/2] " Maxim Ostapenko
2015-11-23  7:48 ` [PATCH 1/2] " Maxim Ostapenko
2015-11-23  8:19   ` Jakub Jelinek
2015-11-23 12:24     ` Christophe Lyon
2015-11-23 12:37       ` Maxim Ostapenko
2015-11-23 12:42         ` Jakub Jelinek
2015-11-23 13:05           ` Christophe Lyon
2015-11-23 13:24             ` Maxim Ostapenko
2015-11-23 13:29               ` Jakub Jelinek
2015-11-24  8:08                 ` Maxim Ostapenko
2015-11-24  8:30                   ` Jakub Jelinek
2015-11-24  8:38                     ` Maxim Ostapenko
2015-11-24  8:43                       ` Jakub Jelinek
2015-11-24  8:58                         ` Maxim Ostapenko
2015-11-24  9:24                           ` Christophe Lyon [this message]
2015-11-24 11:12                             ` Christophe Lyon
2015-11-24 11:23                               ` Jakub Jelinek
2015-11-24 11:23                                 ` Christophe Lyon
2015-11-24 11:34                                   ` Jakub Jelinek
2015-11-24 11:57                                     ` Maxim Ostapenko
2015-11-24 12:06                                       ` Jakub Jelinek
2015-11-24 12:20                                         ` Christophe Lyon
2015-11-24 13:06                                           ` Maxim Ostapenko
2015-11-24 12:09                                       ` Yury Gribov
2015-11-23  8:06 ` [PATCH 2/2] " Maxim Ostapenko
2015-11-23  8:20   ` Jakub Jelinek

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='CAKdteOb8+O=PpTDdX3tZqeAE_4ojO02dujm=PYxwXQqTnvrkBQ@mail.gmail.com' \
    --to=christophe.lyon@linaro.org \
    --cc=adhemerval.zanella@linaro.org \
    --cc=gcc-patches@gcc.gnu.org \
    --cc=jakub@redhat.com \
    --cc=kcc@google.com \
    --cc=m.ostapenko@partner.samsung.com \
    --cc=v.barinov@samsung.com \
    --cc=v.garbuzov@samsung.com \
    --cc=y.gribov@samsung.com \
    /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).