Re: [PATCH v2] [libcc1] Rename C{,P}_COMPILER_NAME and remove triplet from them

On Wednesday, November 15 2017, Jim Wilson wrote: > On 11/13/2017 01:10 PM, Sergio Durigan Junior wrote: >> On Tuesday, September 26 2017, I wrote: >> >>> Ping^2. >> >> Ping^3. >> >> I'm sending the updated ChangeLog/patch. I'm a

Re: [PATCH v2] [libcc1] Rename C{,P}_COMPILER_NAME and remove triplet from them

On Tuesday, September 26 2017, I wrote: > Ping^2. Ping^3. I'm sending the updated ChangeLog/patch. I'm also removing gdb-patches from the Cc list. libcc1/ChangeLog: 2017-09-01 Sergio Durigan Junior Pedro Alves * Makefile.am: Remove references to c-compil

Re: [PATCH v2] [libcc1] Rename C{,P}_COMPILER_NAME and remove triplet from them

Ping^2. On Friday, September 15 2017, I wrote: > Ping. > > On Friday, September 01 2017, I wrote: > >> On Wednesday, August 23 2017, Pedro Alves wrote: >> >>> On 08/23/2017 05:17 AM, Sergio Durigan Junior wrote: >>>> Hi there, >>>> >

Re: [PATCH v2] [libcc1] Rename C{,P}_COMPILER_NAME and remove triplet from them

Ping. On Friday, September 01 2017, I wrote: > On Wednesday, August 23 2017, Pedro Alves wrote: > >> On 08/23/2017 05:17 AM, Sergio Durigan Junior wrote: >>> Hi there, >>> >>> This is a series of two patches, one for GDB and one for GCC, which aims >&

[PATCH v2] [libcc1] Rename C{,P}_COMPILER_NAME and remove triplet from them

On Wednesday, August 23 2017, Pedro Alves wrote: > On 08/23/2017 05:17 AM, Sergio Durigan Junior wrote: >> Hi there, >> >> This is a series of two patches, one for GDB and one for GCC, which aims >> to improve the detection and handling of triplets present on compile

Re: [libcc1] Improve detection of triplet on compiler names

On Wednesday, August 23 2017, Pedro Alves wrote: > On 08/23/2017 05:17 AM, Sergio Durigan Junior wrote: >> Hi there, >> >> This is a series of two patches, one for GDB and one for GCC, which aims >> to improve the detection and handling of triplets present on compile

Re: [libcc1] Improve detection of triplet on compiler names

On Wednesday, August 23 2017, Pedro Alves wrote: > On 08/23/2017 02:07 PM, Sergio Durigan Junior wrote: >> On Wednesday, August 23 2017, Pedro Alves wrote: >> >>> On 08/23/2017 05:17 AM, Sergio Durigan Junior wrote: >>>> The GCC patch improves the libcc

Re: [libcc1] Improve detection of triplet on compiler names

On Wednesday, August 23 2017, Pedro Alves wrote: > On 08/23/2017 05:17 AM, Sergio Durigan Junior wrote: >> The GCC patch improves the libcc1::compiler_triplet_regexp::find and >> libcp1::compiler_triplet_regexp::find methods by first trying to match >> the triplet in

[PATCH 2/2] [GDB] Add trailing dash on triplet regexp

ible http://sergiodj.net/ gdb/ChangeLog: 2017-08-23 Sergio Durigan Junior * compile/compile.c (compile_to_object): Add trailing dash on triplet regexp. diff --git a/gdb/compile/compile.c b/gdb/compile/compile.c index 91e084f89f..0ce77a8b95 100644 --- a/gdb/compile/compile.c +++

[PATCH 1/2] [GCC] Improve regexp handling on libc[cp]1::compiler_triplet_regexp::find

how Fedora names its GCC, by the way). OK to apply? -- Sergio GPG key ID: 237A 54B1 0287 28BF 00EF 31F4 D0EB 7628 65FC 5E36 Please send encrypted e-mail if possible http://sergiodj.net/ libcc1/ChangeLog: 2017-08-23 Sergio Durigan Junior * libcc1.cc (make_regexp): Don't add d

[libcc1] Improve detection of triplet on compiler names

Hi there, This is a series of two patches, one for GDB and one for GCC, which aims to improve the detection and handling of triplets present on compiler names. The motivation for this series was mostly the fact that GDB's "compile" command is broken on Debian unstable, as can be seen here:

Re: [PATCH] Make dg-extract-results.sh explicitly treat .{sum,log} files as text

On Tuesday, December 16 2014, Mike Stump wrote: > Well, I’d still say that ‘\0’ in the output of tools is antisocial and that > is the real bug that needs to be fixed. I agree with you, and I am working on a patch to fix GDB, too. > That aside, it is reasonable to protect testing from poorly be

Re: [PATCH] Make dg-extract-results.sh explicitly treat .{sum,log} files as text

On Tuesday, December 16 2014, Mike Stump wrote: > So, either, the tool should not generate 0 in the output, which, is rather > anti-social, or one should strip the funny characters in a more portable > fashion. > > tr and cat -v come to mind; both should be pretty portable. > >> OK to apply? > >

Re: [PATCH] Make dg-extract-results.sh explicitly treat .{sum,log} files as text

On Tuesday, December 16 2014, Jakub Jelinek wrote: > On Tue, Dec 16, 2014 at 09:36:33AM +, Pedro Alves wrote: >> On 12/15/2014 11:00 PM, Sergio Durigan Junior wrote: >> > +# Check if grep supports the '--text' option. >> > + >> > +GREP_TEXT

Re: [PATCH] Make dg-extract-results.sh explicitly treat .{sum,log} files as text

On Monday, December 15 2014, Jakub Jelinek wrote: > I'd be surprised if all versions of grep supported --text option (e.g. POSIX > doesn't mention the -a nor --text options), guess > you'd need to check for that first (early in the script) and add it only if > it works. Thanks for the review, Jak

[PATCH] Make dg-extract-results.sh explicitly treat .{sum,log} files as text

option to grep, which overrides grep's machinery to identify if the file is binary and forces it to treat every file as text. For me, it makes sense to do that because sum and log files will always be text, no matter what happens. It is also worth noticing that the Python version of dg-

Re: [PATCH] Implement stap probe on ARM's unwinder

Sergio Durigan Junior writes: > Sergio Durigan Junior writes: > >> Bernd Schmidt writes: >> >>> On 12/01/11 13:01, Ramana Radhakrishnan wrote: >>>> Sergio: Other than a few minor tweaks to the Changelog it largely >>>> looks obvious to me. &g

Re: [PATCH] Implement stap probe on ARM's unwinder

Sergio Durigan Junior writes: > Bernd Schmidt writes: > >> On 12/01/11 13:01, Ramana Radhakrishnan wrote: >>> Sergio: Other than a few minor tweaks to the Changelog it largely >>> looks obvious to me. >>> >>> Bernd, could you take another look a

Re: [PATCH] Implement stap probe on ARM's unwinder

repository. Thank you again, Sergio. diff --git a/libgcc/ChangeLog b/libgcc/ChangeLog index e7f18e2..0901cae 100644 --- a/libgcc/ChangeLog +++ b/libgcc/ChangeLog @@ -1,3 +1,14 @@ +2011-12-02 Sergio Durigan Junior + + * unwind-arm-common.inc: Include `tconfig.h', `tsystem.h' a

Re: [PATCH] Implement stap probe on ARM's unwinder

Bernd Schmidt writes: > On 12/01/11 13:01, Ramana Radhakrishnan wrote: >> Sergio: Other than a few minor tweaks to the Changelog it largely >> looks obvious to me. >> >> Bernd, could you take another look at this since this is now shared >> with the c6x backend ? > > Doesn't look like it would c

Re: [PATCH] Implement stap probe on ARM's unwinder

Sergio Durigan Junior writes: > Hello, > > This is the implementation of > <http://gcc.gnu.org/ml/gcc-patches/2011-01/msg01016.html> for the ARM > unwinder. Since ARM has a different unwinder, I basically replicated > the existing code (on unwind-dw2.c) into it, wit

[PATCH] Implement stap probe on ARM's unwinder

og index 305e8ad..f6e9dec 100644 --- a/libgcc/ChangeLog +++ b/libgcc/ChangeLog @@ -1,3 +1,15 @@ +2011-11-22 Sergio Durigan Junior + + Implement ARM Unwinder SystemTap probe. + * unwind-arm-common.inc: Include `tconfig.h', `tsystem.h' and + `sys/sdt.h'. + (_