public inbox for gcc-patches@gcc.gnu.org
 help / color / mirror / Atom feed
From: Sebastian Huber <sebastian.huber@embedded-brains.de>
To: Jeff Law <law@redhat.com>,
	Chung-Lin Tang <chunglin_tang@mentor.com>,
	gcc-patches <gcc-patches@gcc.gnu.org>
Cc: Sandra Loosemore <sandra@codesourcery.com>
Subject: Re: [patch, nios2] Fix PR78357, adjust sync builtin initialization
Date: Thu, 24 Nov 2016 06:57:00 -0000	[thread overview]
Message-ID: <58368F50.9010204@embedded-brains.de> (raw)
In-Reply-To: <2edbdd19-7ac7-c0ba-1ec9-f4849657c418@redhat.com>

Hello Jeff,

On 23/11/16 23:28, Jeff Law wrote:
> On 11/16/2016 02:53 AM, Chung-Lin Tang wrote:
>> This patch adjusts the initialization of __sync built-in functions:
>> instead of conditionalizing on TARGET_LINUX_ABI, directly place the
>> target-hook #define in config/nios2/linux.h.  This appears to be in line
>> with other similar ports, e.g. m68k.
>>
>> Sebastian, this should solve your issue of not wanting __sync_* libcalls
>> generated on RTEMS (which also uses TARGET_LINUX_ABI due to TLS 
>> support),
>> can you verify it works for you?
>>
>> Chung-Lin
>>
>>     PR target/78357
>>     * config/nios2/nios2.c (nios2_init_libfuncs): Remove 
>> TARGET_LINUX_ABI
>>     condition.
>>     (TARGET_INIT_LIBFUNCS): Delete definition and...
>>     * config/nios2/linux.h (TARGET_INIT_LIBFUNCS): ...move to here, add
>>     comments.
>>
> I fear you may have botched this;
>
> g++ -fno-PIE -c   -g  -DIN_GCC  -DCROSS_DIRECTORY_STRUCTURE 
> -fno-exceptions -fno-rtti -fasynchronous-unwind-tables -W -Wall 
> -Wno-narrowing -Wwrite-strings -Wcast-qual -Wmissing-format-attribute 
> -Woverloaded-virtual -pedantic -Wno-long-long -Wno-variadic-macros 
> -Wno-overlength-strings -Werror -fno-common  -DHAVE_CONFIG_H -I. -I. 
> -I/home/law/gcc-testing/gcc/gcc -I/home/law/gcc-testing/gcc/gcc/. 
> -I/home/law/gcc-testing/gcc/gcc/../include 
> -I/home/law/gcc-testing/gcc/gcc/../libcpp/include 
> -I/opt/cfarm/mpc/include 
> -I/home/law/gcc-testing/gcc/gcc/../libdecnumber 
> -I/home/law/gcc-testing/gcc/gcc/../libdecnumber/dpd -I../libdecnumber 
> -I/home/law/gcc-testing/gcc/gcc/../libbacktrace   -o nios2.o -MT 
> nios2.o -MMD -MP -MF ./.deps/nios2.TPo 
> /home/law/gcc-testing/gcc/gcc/config/nios2/nios2.c
> /home/law/gcc-testing/gcc/gcc/config/nios2/nios2.c:3608:1: error: 
> ‘void nios2_init_libfuncs()’ defined but not used 
> [-Werror=unused-function]
>  nios2_init_libfuncs (void)

in my build this was only a warning. How do you enable the -Werror for 
the GCC build? Is this the normal way to build GCC?

-- 
Sebastian Huber, embedded brains GmbH

Address : Dornierstr. 4, D-82178 Puchheim, Germany
Phone   : +49 89 189 47 41-16
Fax     : +49 89 189 47 41-09
E-Mail  : sebastian.huber@embedded-brains.de
PGP     : Public key available on request.

Diese Nachricht ist keine geschäftliche Mitteilung im Sinne des EHUG.

  reply	other threads:[~2016-11-24  6:57 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-11-16  9:54 Chung-Lin Tang
2016-11-16 11:06 ` Sebastian Huber
2016-11-23 22:28 ` Jeff Law
2016-11-24  6:57   ` Sebastian Huber [this message]
2016-11-24 15:31     ` Jeff Law
2016-11-24  9:32   ` Chung-Lin Tang

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=58368F50.9010204@embedded-brains.de \
    --to=sebastian.huber@embedded-brains.de \
    --cc=chunglin_tang@mentor.com \
    --cc=gcc-patches@gcc.gnu.org \
    --cc=law@redhat.com \
    --cc=sandra@codesourcery.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).