public inbox for gcc-patches@gcc.gnu.org
 help / color / mirror / Atom feed
From: Marcus Shawcroft <marcus.shawcroft@gmail.com>
To: Yvan Roux <yvan.roux@linaro.org>
Cc: "gcc-patches@gcc.gnu.org" <gcc-patches@gcc.gnu.org>
Subject: Re: [PATCH, boehm-gc, AArch64] Add AArch64 support
Date: Thu, 11 Apr 2013 12:25:00 -0000	[thread overview]
Message-ID: <CAFqB+PwDWa2swxvOLF52VzDE=_Xbj0ajmGyU8agy9qnqvkR_fA@mail.gmail.com> (raw)
In-Reply-To: <CAD57uCfN=5QG0TmOa3h_J1AvxzqvvH2mOHQmUFM7HCwwURPHSw@mail.gmail.com>

Hi Yvan,  My understanding of the 'Free for all' section of
http://gcc.gnu.org/svnwrite.html#policies is that since this is a
backport from an upstream project you do not need to seek further
approval to commit this change.

Cheers
/Marcus

On 2 April 2013 11:50, Yvan Roux <yvan.roux@linaro.org> wrote:
> Ping (second try)
>
> Sorry if you received it twice, it seems that my gmail account
> switched in text/html mode :(
>
> Many thanks,
> Yvan
>
> On 2 April 2013 11:21, Yvan Roux <yvan.roux@linaro.org> wrote:
>>
>> Ping
>>
>>
>> On 17 March 2013 21:34, Yvan Roux <yvan.roux@linaro.org> wrote:
>>>
>>> Hi,
>>>
>>> this is a backport from gc mainline of the basic AArch64 support (it
>>> covers the Linux and bare machine mode). I tested it on the Foundation
>>> model with enabling the objc frontend, and passing the testsuite
>>> manually (maybe I miss-configured it, but it seems that the boehm-gc
>>> testsuite is not cross-environment friendly, as the gctest script
>>> looks for the host gcc build tree), and everything is fine, except the
>>> thread_leak_test which has a different output than the x86 one:
>>>
>>> x86 thread_leak_test output
>>>
>>> Leaked composite object at 0x2aaaaab05fe0
>>>
>>> (/work/sources/gcc-fsf/bgc/boehm-gc/testsuite/boehm-gc.c/thread_leak_test.c:21,
>>> sz=4, NORMAL)
>>>
>>> Leaked composite object at start: 0x2aaaaab03fa0, appr. length: 40
>>> Leaked composite object at 0x2aaaaab05ec0
>>>
>>> (/work/sources/gcc-fsf/bgc/boehm-gc/testsuite/boehm-gc.c/thread_leak_test.c:21,
>>> sz=4, NORMAL)
>>>
>>> Leaked composite object at 0x2aaaaab05f20
>>>
>>> (/work/sources/gcc-fsf/bgc/boehm-gc/testsuite/boehm-gc.c/thread_leak_test.c:21,
>>> sz=4, NORMAL)
>>>
>>> Leaked composite object at start: 0x2aaaaab03f50, appr. length: 40
>>> Leaked composite object at start: 0x2aaaaab03f78, appr. length: 40
>>> Leaked composite object at 0x2aaaaab05ef0
>>>
>>> (/work/sources/gcc-fsf/bgc/boehm-gc/testsuite/boehm-gc.c/thread_leak_test.c:21,
>>> sz=4, NORMAL)
>>>
>>> Leaked composite object at start: 0x2aaaaab03fa0, appr. length: 40
>>> Leaked composite object at 0x2aaaaab05e00
>>>
>>> (/work/sources/gcc-fsf/bgc/boehm-gc/testsuite/boehm-gc.c/thread_leak_test.c:21,
>>> sz=4, NORMAL)
>>>
>>> Leaked composite object at start: 0x2aaaaab03f78, appr. length: 40
>>>
>>> AArch64 thread_leak_test output:
>>>
>>> Leaked composite object at 0x7f91e14ef0
>>>
>>> (/work/sources/gcc-fsf/bgc/boehm-gc/testsuite/boehm-gc.c/thread_leak_test.c:21,
>>> sz=4, NORMAL)
>>>
>>> Leaked composite object at 0x7f91e14fe0
>>>
>>> (/work/sources/gcc-fsf/bgc/boehm-gc/testsuite/boehm-gc.c/thread_leak_test.c:21,
>>> sz=4, NORMAL)
>>>
>>> Leaked composite object at 0x7f91e14e00
>>>
>>> (/work/sources/gcc-fsf/bgc/boehm-gc/testsuite/boehm-gc.c/thread_leak_test.c:21,
>>> sz=4, NORMAL)
>>>
>>> Leaked composite object at 0x7f91e14e30
>>>
>>> (/work/sources/gcc-fsf/bgc/boehm-gc/testsuite/boehm-gc.c/thread_leak_test.c:21,
>>> sz=4, NORMAL)
>>>
>>> Leaked composite object at 0x7f91e14fe0
>>>
>>> (/work/sources/gcc-fsf/bgc/boehm-gc/testsuite/boehm-gc.c/thread_leak_test.c:21,
>>> sz=4, NORMAL)
>>>
>>>
>>> Regards,
>>> Yvan
>>>
>>> 2013-03-16  Yvan Roux <yvan.roux@linaro.org>
>>>
>>>         * include/private/gcconfig.h (AARCH64): New macro (defined
>>> only if
>>>         __aarch64__).
>>>         * include/private/gcconfig.h (mach_type_known): Update comment
>>> adding
>>>         ARM AArch64 target.
>>>         * include/private/gcconfig.h (NOSYS, mach_type_known,
>>> CPP_WORDSZ,
>>>         MACH_TYPE, ALIGNMENT, HBLKSIZE, OS_TYPE, LINUX_STACKBOTTOM,
>>>         USE_GENERIC_PUSH_REGS, DYNAMIC_LOADING, DATASTART, DATAEND,
>>>         STACKBOTTOM): Define for AArch64.
>>
>>

  reply	other threads:[~2013-04-11 11:02 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-03-17 20:34 Yvan Roux
     [not found] ` <CAD57uCfa2K7bux0siwxK_+ktDzwxbN9VQJTTU=SMOOXkWCm2iQ@mail.gmail.com>
2013-04-02 11:31   ` Yvan Roux
2013-04-11 12:25     ` Marcus Shawcroft [this message]
2013-04-11 12:33       ` Yvan Roux
2013-05-02 19:51         ` Christophe Lyon

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='CAFqB+PwDWa2swxvOLF52VzDE=_Xbj0ajmGyU8agy9qnqvkR_fA@mail.gmail.com' \
    --to=marcus.shawcroft@gmail.com \
    --cc=gcc-patches@gcc.gnu.org \
    --cc=yvan.roux@linaro.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).