X-Spam-Check-By: sourceware.org From: "Dave Korn" To: "'Aaron Gray'" , Cc: "'GCC'" References: <2b2c01c78fa5$d94a27c0$0200a8c0 AT AMD2500> <01f001c78fc6$c916ce00$2e08a8c0 AT CAM DOT ARTIMI DOT COM> <005501c78fe3$b1a9ec80$0200a8c0 AT AMD2500> Subject: RE: Successful build of GCC 4.2.0 RC3 on latest Cygwin snapshot 20070427 Date: Sun, 6 May 2007 15:54:26 +0100 Message-ID: <022501c78fee$71302ec0$2e08a8c0@CAM.ARTIMI.COM> MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit X-Mailer: Microsoft Office Outlook 11 In-Reply-To: <005501c78fe3$b1a9ec80$0200a8c0@AMD2500> Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm Precedence: bulk List-Id: List-Unsubscribe: List-Subscribe: List-Archive: List-Post: List-Help: , Sender: cygwin-owner AT cygwin DOT com Mail-Followup-To: cygwin AT cygwin DOT com Delivered-To: mailing list cygwin AT cygwin DOT com On 06 May 2007 14:37, Aaron Gray wrote: > On the LLVM build I am getting multiple :- > > warning: visibility attribute not supported in this configuration; > ignored > > with the same line number, eight or so in some cases but usually two. > > Have not looked into this properly yet, I missed it earlier when first > building but on rebuilding have captured it in a log file for thurther > examination. IIUIC, the visibility attribute is only relevant to ELF targets, which cygwin is not. Hence the warnings, while seemingly redundant, are at least accurate[*]. The visibility attribute needs wrapped in a macro that can be undef'd on non-ELF systems. > I can put together a test example if required. If you can produce once that shows excess warnings being emitted, yes, that would be worth filing a PR. Hmm, a quick test I couldn't get excess ones, but the line numbers all look wrong.. cheers, DaveK [*] - and without seeing the actual code I don't even know that there aren't that many attributed decls on the same line... -- Can't think of a witty .sigline today.... -- Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple Problem reports: http://cygwin.com/problems.html Documentation: http://cygwin.com/docs.html FAQ: http://cygwin.com/faq/