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 compiler
>> names. The motivation
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 compiler
> names. The motivation for this series was mostly the fact that GDB's
> "compile"
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 libcc1::compiler_triplet_regexp::find and
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 libcc1::compiler_triplet_regexp::find and
>>> libcp1::compiler_triplet_regexp::find methods by first
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 the compiler name and
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 the compiler name and correctly discarding the triplet
> part of the regexp if the
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: