public inbox for openembedded-core@lists.openembedded.org
 help / color / mirror / Atom feed
From: "Hemraj, Deepthi" <Deepthi.Hemraj@windriver.com>
To: openembedded-core@lists.openembedded.org
Subject: Re: [PATCH] gcc-sanitizers: Add ptest support for AddressSanitizer tests
Date: Tue, 03 Sep 2024 23:42:47 -0700	[thread overview]
Message-ID: <17622.1725432167987381530@lists.openembedded.org> (raw)
In-Reply-To: <bd31fb7301b3ebb5c8dcedbe29ef30aab1d99a21.camel@linuxfoundation.org>

[-- Attachment #1: Type: text/plain, Size: 908 bytes --]

Hi Richard,

Thanks for checking the patch and your comment
"Would it make more sense to run this as part of the other gcc testsuites?"

Definitely Yes. We can add the sanitizer tests as part of the existing gcc testsuites.

However, the sanitizer test was intentionally kept separate to avoid unnecessary building and testing of sanitizers that are not required for most users.

The current activity was taken up when checking the sanitizers support for all targets. This testsuite will just test the sanitizers support quickly within few minutes. Running the complete testsuite to check the sanitizers would require few hours. Hence, we had planned and implemented the ptest specifically for sanitizer support.

However, we will add it as part of the complete testsuite if that seems most profitable for everyone. Please let us know your views on the same so that we can work towards the same.

[-- Attachment #2: Type: text/html, Size: 3089 bytes --]

WARNING: multiple messages have this Message-ID (diff)
From: "Hemraj, Deepthi" <Deepthi.Hemraj@windriver.com>
To: openembedded-core@lists.openembedded.org
Subject: Re: [PATCH] gcc-sanitizers: Add ptest support for AddressSanitizer tests
Date: Tue, 03 Sep 2024 23:43:26 -0700	[thread overview]
Message-ID: <17622.1725432167987381530@lists.openembedded.org> (raw)
Message-ID: <20240904064326.xtxiAUHbUK6nuvov5QbeFp4ZlCMPCpj5lncJEdMfFi4@z> (raw)
In-Reply-To: <bd31fb7301b3ebb5c8dcedbe29ef30aab1d99a21.camel@linuxfoundation.org>

[-- Attachment #1: Type: text/plain, Size: 928 bytes --]

Hi Richard,

Thanks for checking the patch and your comment
"Would it make more sense to run this as part of the other gcc testsuites?"

Definitely Yes. We can add the sanitizer tests as part of the existing gcc testsuites.

However, the sanitizer test was intentionally kept separate to avoid unnecessary building and testing of sanitizers that are not required for most users.

The current activity was taken up when checking the sanitizers support for all targets. This testsuite will just test the sanitizers support quickly within few minutes. Running the complete testsuite to check the sanitizers would require few hours. Hence, we had planned and implemented the ptest specifically for sanitizer support.

However, we will add it as part of the complete testsuite if that seems most profitable for everyone. Please let us know your views on the same so that we can work towards the same.

Thanks,
Deepthi

[-- Attachment #2: Type: text/html, Size: 2529 bytes --]

  reply	other threads:[~2024-09-04  6:42 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-09-02  7:39 [PATCH] gcc-sanitizers: Add ptest support for AddressSanitizer tests Deepthi.Hemraj
2024-09-02  7:48 ` Patchtest results for " patchtest
2024-09-02  9:07 ` [OE-core] " Richard Purdie
2024-09-04  6:42   ` Hemraj, Deepthi [this message]
2024-09-04  6:43     ` Hemraj, Deepthi

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=17622.1725432167987381530@lists.openembedded.org \
    --to=deepthi.hemraj@windriver.com \
    --cc=openembedded-core@lists.openembedded.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