Re: How to avoding compiling unreferenced code into .o target file

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

To: kipade <kipade@xxxxxxx>, gcc-help@xxxxxxxxxxx
Subject: Re: How to avoding compiling unreferenced code into .o target file
From: Andrew Haley <aph@xxxxxxxxxx>
Date: Thu, 31 Aug 2017 10:37:10 +0100
Dmarc-filter: OpenDMARC Filter v1.3.2 mx1.redhat.com 6FDAE155E0
In-reply-to: <65beb0b1-4d63-6ee8-3c6b-de7360c5430c@163.com>
References: <65beb0b1-4d63-6ee8-3c6b-de7360c5430c@163.com>
User-agent: Mozilla/5.0 (X11; Linux x86_64; rv:52.0) Gecko/20100101 Thunderbird/52.2.0

On 31/08/17 10:31, kipade wrote:
> Any hints will be very very appreciated.

A small example of the problem would help.

-- 
Andrew Haley
Java Platform Lead Engineer
Red Hat UK Ltd. <https://www.redhat.com>
EAC8 43EB D3EF DB98 CC77 2FAD A5CD 6035 332F A671

Follow-Ups:
- Re: How to avoding compiling unreferenced code into .o target file
  - From: kipade

References:
- How to avoding compiling unreferenced code into .o target file
  - From: kipade

Prev by Date: How to avoding compiling unreferenced code into .o target file
Next by Date: Re: How to avoding compiling unreferenced code into .o target file
Previous by thread: How to avoding compiling unreferenced code into .o target file
Next by thread: Re: How to avoding compiling unreferenced code into .o target file
Index(es):
- Date
- Thread

[Index of Archives] [Linux C Programming] [Linux Kernel] [eCos] [Fedora Development] [Fedora Announce] [Autoconf] [The DWARVES Debugging Tools] [Yosemite Campsites] [Yosemite News] [Linux GCC]

Powered by Linux