On 6/7/19 6:57 AM, Christophe Lyon wrote:
On Wed, 5 Jun 2019 at 20:33, Martin Sebor wrote:
On 5/31/19 12:20 PM, Jeff Law wrote:
On 5/31/19 9:56 AM, Martin Sebor wrote:
On 5/30/19 5:49 PM, Jeff Law wrote:
So in several places there's a comment which indicates that debugging
dumps and the lik
On Wed, 5 Jun 2019 at 20:33, Martin Sebor wrote:
>
> On 5/31/19 12:20 PM, Jeff Law wrote:
> > On 5/31/19 9:56 AM, Martin Sebor wrote:
> >> On 5/30/19 5:49 PM, Jeff Law wrote:
> >>> So in several places there's a comment which indicates that debugging
> >>> dumps and the like do not follow conventi
On 6/6/19 9:42 AM, Jakub Jelinek wrote:
On Thu, Jun 06, 2019 at 08:45:56AM -0600, Martin Sebor wrote:
Changes for the same change shouldn't be separated by empty newlines in the
ChangeLog. Furthermore, you've managed to commit only the first part (until
varasm.c) and not the rest.
I actually
On Thu, Jun 06, 2019 at 08:45:56AM -0600, Martin Sebor wrote:
> > Changes for the same change shouldn't be separated by empty newlines in the
> > ChangeLog. Furthermore, you've managed to commit only the first part (until
> > varasm.c) and not the rest.
>
> I actually managed to do that on purpos
On 6/6/19 3:39 AM, Jakub Jelinek wrote:
On Wed, May 22, 2019 at 10:34:00AM -0600, Martin Sebor wrote:
gcc/ChangeLog:
* config/i386/i386-features.c (ix86_get_function_versions_dispatcher):
Adjust quoting and hyphenation.
* convert.c (convert_to_real_1): Same.
* gc
On Wed, May 22, 2019 at 10:34:00AM -0600, Martin Sebor wrote:
> gcc/ChangeLog:
>
> * config/i386/i386-features.c (ix86_get_function_versions_dispatcher):
> Adjust quoting and hyphenation.
> * convert.c (convert_to_real_1): Same.
> * gcc.c (driver_wrong_lang_callback): Same.
On 5/31/19 12:20 PM, Jeff Law wrote:
On 5/31/19 9:56 AM, Martin Sebor wrote:
On 5/30/19 5:49 PM, Jeff Law wrote:
So in several places there's a comment which indicates that debugging
dumps and the like do not follow conventions. Presumably you've tried
to keep a narrow scope on the diagnostic
On 5/31/19 9:56 AM, Martin Sebor wrote:
> On 5/30/19 5:49 PM, Jeff Law wrote:
>> So in several places there's a comment which indicates that debugging
>> dumps and the like do not follow conventions. Presumably you've tried
>> to keep a narrow scope on the diagnostic push/pops. I'm also concerned
On 5/30/19 5:49 PM, Jeff Law wrote:
On 5/22/19 10:34 AM, Martin Sebor wrote:
Incorporating the feedback I got on the -Wformat-diag checker
provided an opportunity to tighten up existing and implement
a small number of few additional rules based on GCC Coding
Conventions (https://gcc.gnu.org/codi
On 5/22/19 10:34 AM, Martin Sebor wrote:
> Incorporating the feedback I got on the -Wformat-diag checker
> provided an opportunity to tighten up existing and implement
> a small number of few additional rules based on GCC Coding
> Conventions (https://gcc.gnu.org/codingconventions.html).
> The chec
Incorporating the feedback I got on the -Wformat-diag checker
provided an opportunity to tighten up existing and implement
a small number of few additional rules based on GCC Coding
Conventions (https://gcc.gnu.org/codingconventions.html).
The checker now also warns for incorrect uses of the follo
11 matches
Mail list logo
