> -Original Message-
> From: Marek Polacek [mailto:pola...@redhat.com]
> Sent: 24 September 2013 14:52
> To: Paulo Matos
> Cc: gcc-patches@gcc.gnu.org
> Subject: Re: [PATCH] Fix typo in check for null
>
> On Tue, Sep 24, 2013 at 01:44:30PM +, Paulo Matos w
On Tue, Sep 24, 2013 at 01:44:30PM +, Paulo Matos wrote:
> Thanks for the comments Marek, will fix it.
>
> 2013-09-24 Paulo Matos
^^
Two spaces between name and . Sorry for nitpicking like
this. Thanks!
Marek
> -Original Message-
> From: Richard Biener [mailto:richard.guent...@gmail.com]
> Sent: 24 September 2013 10:03
> To: Paulo Matos
> Cc: gcc-patches@gcc.gnu.org
> Subject: Re: [PATCH] Fix typo in check for null
>
> On Mon, Sep 23, 2013 at 4:03 PM, Paulo Matos wr
> -Original Message-
> From: Marek Polacek [mailto:pola...@redhat.com]
> Sent: 24 September 2013 13:57
> To: Paulo Matos
> Cc: gcc-patches@gcc.gnu.org
> Subject: Re: [PATCH] Fix typo in check for null
>
> On Mon, Sep 23, 2013 at 02:03:02PM +, Paulo Matos wrote:
On Mon, Sep 23, 2013 at 02:03:02PM +, Paulo Matos wrote:
> This is a patch for master, where in number_of_loops, we want to check if the
> loops (returned by loops_for_fn) is non-null but instead we are using fn,
> which is the function argument. I haven't opened a bug report, please let me
On Mon, Sep 23, 2013 at 4:03 PM, Paulo Matos wrote:
> This is a patch for master, where in number_of_loops, we want to check if the
> loops (returned by loops_for_fn) is non-null but instead we are using fn,
> which is the function argument. I haven't opened a bug report, please let me
> know i