public inbox for gcc-patches@gcc.gnu.org
 help / color / mirror / Atom feed
From: Ian Lance Taylor <ian@airs.com>
To: Yury Gribov <y.gribov@samsung.com>
Cc: GCC Patches <gcc-patches@gcc.gnu.org>,
	 Konstantin Serebryany <konstantin.s.serebryany@gmail.com>,
	 Dmitry Vyukov <dvyukov@google.com>,
	Andrey Ryabinin <a.ryabinin@samsung.com>
Subject: Re: [PATCHv5][Kasan] Allow to override Asan shadow offset from command line
Date: Mon, 27 Oct 2014 16:02:00 -0000	[thread overview]
Message-ID: <m38uk18pxr.fsf@pepe.airs.com> (raw)
In-Reply-To: <544A5A95.6030502@samsung.com> (Yury Gribov's message of "Fri, 24	Oct 2014 17:56:37 +0400")

Yury Gribov <y.gribov@samsung.com> writes:

> --- a/include/libiberty.h
> +++ b/include/libiberty.h
> @@ -655,6 +655,33 @@ extern size_t strnlen (const char *, size_t);
>  extern int strverscmp (const char *, const char *);
>  #endif
>  
> +#if defined(HAVE_DECL_STRTOL) && !HAVE_DECL_STRTOL
> +extern long int strtol (const char *nptr,
> +                        char **endptr, int base);
> +#endif
> +
> +#if defined(HAVE_DECL_STRTOUL) && !HAVE_DECL_STRTOUL
> +extern unsigned long int strtoul (const char *nptr,
> +                                  char **endptr, int base);
> +#endif
> +
> +#if defined(HAVE_DECL_STRTOLL) && !HAVE_DECL_STRTOLL
> +__extension__
> +extern long long int strtoll (const char *nptr,
> +                              char **endptr, int base);
> +#endif
> +
> +#if defined(HAVE_DECL_STRTOULL) && !HAVE_DECL_STRTOULL
> +__extension__
> +extern unsigned long long int strtoull (const char *nptr,
> +                                        char **endptr, int base);
> +#endif


Your patch is otherwise careful to check that only use "long long" if
the compiler supports it.  Here you are not.  I think you need to wrap
the declarations of strtoll and strtoull in

#ifdef HAVE_LONG_LONG

With that change the libiberty/include patch is OK.

Thanks.

Ian

  parent reply	other threads:[~2014-10-27 15:58 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-09-08 14:29 [PATCH][Kasan] " Yury Gribov
2014-09-15  9:46 ` [PATCH][Kasan][PING] " Yury Gribov
2014-09-18 11:01   ` Jakub Jelinek
2014-09-18 11:05     ` Yury Gribov
2014-09-29 17:21   ` [PATCHv3][Kasan][PING] " Yury Gribov
2014-10-06 11:06     ` [PATCHv3][Kasan][PING^2] " Yury Gribov
2014-10-06 11:17       ` Yury Gribov
2014-10-15 16:19         ` [PATCHv3][Kasan][PING^3] " Yury Gribov
2014-10-15 16:54           ` Jakub Jelinek
2014-10-17  7:59     ` [PATCHv4][Kasan] " Yury Gribov
2014-10-17 11:25       ` Jakub Jelinek
2014-10-17 12:32         ` Ian Lance Taylor
2014-10-21 10:02           ` Yury Gribov
2014-10-24 13:58       ` [PATCHv5][Kasan] " Yury Gribov
2014-10-24 14:09         ` Jakub Jelinek
2014-10-27 16:02         ` Ian Lance Taylor [this message]
2014-11-05 14:50         ` Kirill Yukhin
2014-11-12 16:22           ` H.J. Lu

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=m38uk18pxr.fsf@pepe.airs.com \
    --to=ian@airs.com \
    --cc=a.ryabinin@samsung.com \
    --cc=dvyukov@google.com \
    --cc=gcc-patches@gcc.gnu.org \
    --cc=konstantin.s.serebryany@gmail.com \
    --cc=y.gribov@samsung.com \
    /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).