[previous Subject: Re: dejagnu version update? [CORRECTION: not a
regression in DejaGnu; GDB testsuite bug] ]
[adding Tom Tromey to CC list per advice from Rob Savoye]
[adding main DejaGnu mailing list to CC list]
In brief for those new to this, the GDB testsuite is currently broken
when run w
On Wed, Jun 10, 2020 at 06:52:10PM +0300, Alexander Popov wrote:
> On 09.06.2020 21:47, Kees Cook wrote:
> > On Thu, Jun 04, 2020 at 04:49:55PM +0300, Alexander Popov wrote:
> >> Add 'verbose' plugin parameter for stackleak gcc plugin.
> >> It can be used for printing additional info about the kern
On Wed, Jun 10, 2020 at 06:47:14PM +0300, Alexander Popov wrote:
> On 09.06.2020 21:46, Kees Cook wrote:
> The inline asm statement that is used for instrumentation is arch-specific.
> Trying to add
> asm volatile("call stackleak_track_stack")
> in gcc plugin on aarch64 makes gcc break spectacula
[cc-ing Joel as the originator, and ]
On Tue, 9 Jun 2020, Jacob Bachmeyer wrote:
> >> I ran a quick bisection and the culprit turned out to be:
> >>
> >> ba60272a5ac6f6a7012acca03f596a6ed003f044 is the first bad commit
> >> commit ba60272a5ac6f6a7012acca03f596a6ed003f044
> >> Author: Jacob Bachme
On Wed, Jun 10, 2020 at 05:47:54PM +0200, Thomas Schwinge wrote:
> The automated system runs once a day. I guess it's generally deemed
> acceptable if the source code state (commits) and the 'ChangeLog' files
> state is out of sync for one day. There surely must be some mechanism in
> place to ma
On 09.06.2020 21:47, Kees Cook wrote:
> On Thu, Jun 04, 2020 at 04:49:55PM +0300, Alexander Popov wrote:
>> Add 'verbose' plugin parameter for stackleak gcc plugin.
>> It can be used for printing additional info about the kernel code
>> instrumentation.
>>
>> For using it add the following to scrip
Hi!
On 2020-06-10T17:15:41+0200, Tobias Burnus wrote:
> On 6/10/20 3:34 PM, Kwok Cheung Yeung wrote:
>> This patch updates the previous entry on the website for
>> devel/omp/gcc-9 to refer to the new branch instead. This removes
>> references to the old branch, as new development should occur on
On 09.06.2020 21:46, Kees Cook wrote:
> On Thu, Jun 04, 2020 at 04:49:54PM +0300, Alexander Popov wrote:
>> Let's improve the instrumentation to avoid this:
>>
>> 1. Make stackleak_track_stack() save all register that it works with.
>> Use no_caller_saved_registers attribute for that function. This
On 09.06.2020 21:39, Kees Cook wrote:
> On Thu, Jun 04, 2020 at 06:23:38PM +0300, Alexander Popov wrote:
>> On 04.06.2020 17:01, Jann Horn wrote:
>>> On Thu, Jun 4, 2020 at 3:51 PM Alexander Popov wrote:
Some time ago Variable Length Arrays (VLA) were removed from the kernel.
The kernel
On 10.06.2020 10:30, Will Deacon wrote:
> On Tue, Jun 09, 2020 at 12:09:27PM -0700, Kees Cook wrote:
>> On Thu, Jun 04, 2020 at 02:58:06PM +0100, Will Deacon wrote:
>>> On Thu, Jun 04, 2020 at 04:49:57PM +0300, Alexander Popov wrote:
Don't try instrumenting functions in
arch/arm64/kernel
On 09.06.2020 22:15, Kees Cook wrote:
> On Thu, Jun 04, 2020 at 04:49:52PM +0300, Alexander Popov wrote:
>> In this patch series I collected various improvements of the stackleak
>> gcc plugin.
>
> Thanks!
>
>> Alexander Popov (5):
>> gcc-plugins/stackleak: Exclude alloca() from the instrumenta
Thanks both!
Cheers,
Tamar
> -Original Message-
> From: Martin Liška
> Sent: Wednesday, June 10, 2020 2:41 PM
> To: Tamar Christina ; Jonathan Wakely
>
> Cc: Jakub Jelinek ; gcc@gcc.gnu.org; gcc-patches patc...@gcc.gnu.org>
> Subject: Re: [IMPORTANT] ChangeLog related changes
>
> On 6
On 6/10/20 3:34 PM, Tamar Christina wrote:
Hi All,
Hello.
We've been wondering since we no longer list authors in the changelog (at least
mklog doesn't generate it),
You are right, it's preferred solution and it's documented here:
https://gcc.gnu.org/codingconventions.html#ChangeLogs
'''
On Wed, Jun 10, 2020 at 01:34:54PM +, Tamar Christina wrote:
> Hi All,
>
> We've been wondering since we no longer list authors in the changelog (at
> least mklog doesn't generate it),
> How do we handle multi author patches nowadays?
>
> Tried searching for it on the website but couldn’t fi
Hi All,
We've been wondering since we no longer list authors in the changelog (at least
mklog doesn't generate it),
How do we handle multi author patches nowadays?
Tried searching for it on the website but couldn’t find anything.
Thanks,
Tamar
> -Original Message-
> From: Gcc-patches
On 6/9/20 10:29 PM, Jonathan Wakely wrote:
OK, here's a proper patch for the changes you liked, dropping the
changes to the Error exception type.
pytest contrib/gcc-changelog/test_email.py passes.
OK for master?
I like it and I've just pushed the patch to master.
Martin
On Tue, Jun 09, 2020 at 12:09:27PM -0700, Kees Cook wrote:
> On Thu, Jun 04, 2020 at 02:58:06PM +0100, Will Deacon wrote:
> > On Thu, Jun 04, 2020 at 04:49:57PM +0300, Alexander Popov wrote:
> > > Don't try instrumenting functions in
> > > arch/arm64/kernel/vdso/vgettimeofday.c.
> > > Otherwise th
17 matches
Mail list logo
