public inbox for gdb-testers@sourceware.org
help / color / mirror / Atom feed
From: sergiodj+buildbot@sergiodj.net
To: gdb-testers@sourceware.org
Subject: [binutils-gdb] Return unique_xmalloc_ptr from macro scope functions
Date: Thu, 08 Feb 2018 19:32:00 -0000 [thread overview]
Message-ID: <f6c2623eb8ac7296b6d7a76657394272a71f5aee@gdb-build> (raw)
*** TEST RESULTS FOR COMMIT f6c2623eb8ac7296b6d7a76657394272a71f5aee ***
Author: Tom Tromey <tom@tromey.com>
Branch: master
Commit: f6c2623eb8ac7296b6d7a76657394272a71f5aee
Return unique_xmalloc_ptr from macro scope functions
This changes the macro scope functions (sal_macro_scope,
user_macro_scope, and default_macro_scope) to return a
unique_xmalloc_ptr, then fixes up the users. This allowed for the
removal of several cleanups.
2018-02-08 Tom Tromey <tom@tromey.com>
* symtab.c (default_collect_symbol_completion_matches_break_on):
Use unique_xmalloc_ptr.
* macroscope.h: (sal_macro_scope, user_macro_scope)
(default_macro_scope): Return unique_xmalloc_ptr.
* macroscope.c (sal_macro_scope, user_macro_scope)
(default_macro_scope): Return unique_xmalloc_ptr.
* macroexp.h (macro_expand, macro_expand_once): Return
unique_xmalloc_ptr.
* macroexp.c (macro_expand, macro_expand_once): Return
unique_xmalloc_ptr.
* macrocmd.c (macro_expand_command, macro_expand_once_command)
(info_macro_command, info_macros_command): Use
unique_xmalloc_ptr.
* compile/compile-c-support.c (write_macro_definitions): Use
unique_xmalloc_ptr.
* c-exp.y (c_parse): Use unique_xmalloc_ptr.
next reply other threads:[~2018-02-08 19:32 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-02-08 19:32 sergiodj+buildbot [this message]
2018-02-08 19:32 ` Failures on RHEL-s390x-m64, branch master sergiodj+buildbot
2018-02-08 20:18 ` Failures on Fedora-s390x-m64, " sergiodj+buildbot
2018-02-08 20:40 ` Failures on Debian-s390x-m64, " sergiodj+buildbot
2018-02-08 20:54 ` Failures on Debian-s390x-native-extended-gdbserver-m64, " sergiodj+buildbot
2018-02-08 21:08 ` Failures on Debian-s390x-native-gdbserver-m64, " sergiodj+buildbot
2018-02-08 21:13 ` Failures on Fedora-i686, " sergiodj+buildbot
2018-02-08 21:32 ` Failures on Fedora-x86_64-native-extended-gdbserver-m32, " sergiodj+buildbot
2018-02-08 21:59 ` Failures on Fedora-x86_64-m32, " sergiodj+buildbot
2018-02-08 22:14 ` Failures on Fedora-x86_64-native-gdbserver-m64, " sergiodj+buildbot
2018-02-08 23:11 ` Failures on Ubuntu-AArch64-m64, " sergiodj+buildbot
2018-02-09 0:20 ` Failures on Ubuntu-AArch32-native-extended-gdbserver-m32, " sergiodj+buildbot
2018-02-09 1:24 ` Failures on Ubuntu-AArch32-m32, " sergiodj+buildbot
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=f6c2623eb8ac7296b6d7a76657394272a71f5aee@gdb-build \
--to=sergiodj+buildbot@sergiodj.net \
--cc=gdb-testers@sourceware.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).