Re: code size

Previous Topic Next Topic
 
classic Classic list List threaded Threaded
1 message Options
Reply | Threaded
Open this post in threaded view
|  
Report Content as Inappropriate

Re: code size

John N Pham
Hi,

I'm also getting the same errors, which varies a bit depending on
optimization level.

With -O3:
Keccak-simple.c: In function ‘crypto_hash_keccakc512_simple’:
Keccak-simple.c:91:1: warning: visibility attribute not supported in
this configuration; ignored [-Wattributes]
 }
 ^
XBD_APP.c: In function ‘FRW_msgRecHand’:
XBD_APP.c:545:1: warning: visibility attribute not supported in this
configuration; ignored [-Wattributes]
 }
 ^
At top level:
lto1: warning: visibility attribute not supported in this
configuration; ignored [-Wattributes]
lto1: warning: visibility attribute not supported in this
configuration; ignored [-Wattributes]
lto1: warning: visibility attribute not supported in this
configuration; ignored [-Wattributes]
lto1: warning: visibility attribute not supported in this
configuration; ignored [-Wattributes]
lto1: warning: visibility attribute not supported in this
configuration; ignored [-Wattributes]
lto1: warning: visibility attribute not supported in this
configuration; ignored [-Wattributes]
lto1: warning: visibility attribute not supported in this
configuration; ignored [-Wattributes]
lto1: warning: visibility attribute not supported in this
configuration; ignored [-Wattributes]
lto1: warning: visibility attribute not supported in this
configuration; ignored [-Wattributes]
lto1: warning: visibility attribute not supported in this
configuration; ignored [-Wattributes]
lto1: warning: visibility attribute not supported in this
configuration; ignored [-Wattributes]
lto1: warning: visibility attribute not supported in this
configuration; ignored [-Wattributes]
XBD_HAL.c: In function ‘XBD_countStack’:
XBD_HAL.c:235:1: warning: visibility attribute not supported in this
configuration; ignored [-Wattributes]
 }
 ^
At top level:
lto1: warning: visibility attribute not supported in this
configuration; ignored [-Wattributes]
lto1: warning: visibility attribute not supported in this
configuration; ignored [-Wattributes]
lto1: warning: visibility attribute not supported in this
configuration; ignored [-Wattributes]
lto1: warning: visibility attribute not supported in this
configuration; ignored [-Wattributes]
lto1: warning: visibility attribute not supported in this
configuration; ignored [-Wattributes]
lto1: warning: visibility attribute not supported in this
configuration; ignored [-Wattributes]
lto1: warning: visibility attribute not supported in this
configuration; ignored [-Wattributes]
lto1: warning: visibility attribute not supported in this
configuration; ignored [-Wattributes]
lto1: warning: visibility attribute not supported in this
configuration; ignored [-Wattributes]
lto1: warning: visibility attribute not supported in this
configuration; ignored [-Wattributes]

With -Os:
XBD_APP.c: In function ‘FRW_msgTraHand’:
XBD_APP.c:606:1: warning: visibility attribute not supported in this
configuration; ignored [-Wattributes]
 }
 ^
XBD_APP.c: In function ‘FRW_msgRecHand’:
XBD_APP.c:545:1: warning: visibility attribute not supported in this
configuration; ignored [-Wattributes]
 }
 ^
At top level:
lto1: warning: visibility attribute not supported in this
configuration; ignored [-Wattributes]
lto1: warning: visibility attribute not supported in this
configuration; ignored [-Wattributes]
lto1: warning: visibility attribute not supported in this
configuration; ignored [-Wattributes]
lto1: warning: visibility attribute not supported in this
configuration; ignored [-Wattributes]
lto1: warning: visibility attribute not supported in this
configuration; ignored [-Wattributes]
lto1: warning: visibility attribute not supported in this
configuration; ignored [-Wattributes]
XBD_debug.c: In function ‘XBD_debugOutHex32Bit’:
XBD_debug.c:29:1: warning: visibility attribute not supported in this
configuration; ignored [-Wattributes]
 }
 ^
XBD_debug.c: In function ‘XBD_debugOutHexByte’:
XBD_debug.c:12:1: warning: visibility attribute not supported in this
configuration; ignored [-Wattributes]
 }
 ^
XBD_crc.c: In function ‘crc16buffer’:
XBD_crc.c:27:1: warning: visibility attribute not supported in this
configuration; ignored [-Wattributes]
 }
 ^
XBD_HAL.c: In function ‘XBD_countStack’:
XBD_HAL.c:235:1: warning: visibility attribute not supported in this
configuration; ignored [-Wattributes]
 }
 ^
XBD_HAL.c: In function ‘XBD_paintStack’:
XBD_HAL.c:220:1: warning: visibility attribute not supported in this
configuration; ignored [-Wattributes]
 }
 ^
At top level:
lto1: warning: visibility attribute not supported in this
configuration; ignored [-Wattributes]
lto1: warning: visibility attribute not supported in this
configuration; ignored [-Wattributes]



I don't have a reduced test case, but I can release my code. I've posted it at:
http://knzl.me/compile.tar.gz , with gcc command line used in compile.sh

On 2014-12-16 14:39:24
Eric Price <price@sm...> wrote:

> On Tue, 16 Dec 2014 10:47:30 +0000
> Nicholas Clifton <nickc@...> wrote:
>
> > Hi Eric,
> >
> > > there are still some bugs, for example if linking a lot of code
> > > together the compiler suddenly issues a lot of
> > >
> > >> warning: visibility attribute not supported in this configuration;
> > >> ignored [-Wattributes]
> > >
> > > warnings for no apparent reason in random places in the code.
> >
> > That sounds interesting.  Could you send me a small testcase to
> > reproduce the problem ?  Or better yet file a bug report (with the
> > FSF or TI) including the testcase, and then I can look into it.
> >
> > Cheers
> >    Nick
> >
> >
>
> The only test case I have so far that reproduces it contains a lot of
> proprietary code that I unfortunately cannot share here. I yet have to
> create an artificial simplified test case.
>
> The problem is, I was only able to reproduce it when linking together
> a relatively large code base with lots of functions, and only when many
> of these functions were actually being used.
>
> Any attempt to simplify the test case by reducing code, or even
> just calls to that code - which was the first thing I tried, made the
> error "magically" disappear. That happened regardless of which function
> calls were eliminated.
>
> That way I couldn't pinpoint any specific code as the culprit, it
> rather looks like the error only appears when a certain code complexity
> is surpassed. I'd guess maybe because it overwhelms the linker garbage
> collector or makes it switch optimization schemes internally or
> something. It's hard to tell without more detailed knowledge of whats
> going on linker-internally.
>
> Assume the following program was triggering the bug (with function1
> and 2 implemented in previously compiled and now to be linked in object
> files)
>
> void function1(void);
> void function2(void);
>
> int main() {
> function1();
> function2();
> exit 0;
> }
>
> then these two simplified programs both did not trigger it:
>
> int main() {
> function1();
> /* function2(); */
> exit 0;
> }
>
> int main() {
> /* function1(); */
> function2();
> exit 0;
> }
>
>
>
>
> --
> Eric Price
> TTI GmbH - TGU Smartmote
> Pfaffenwaldring 4
> D-70569 Stuttgart
>
> Tel.: +49 0711 - 6856 5369
> Fax.: +49 0711 - 6856 6818
> E-mail: price@...
> Homepage: http://www.smartmote.de
>
>

------------------------------------------------------------------------------
Dive into the World of Parallel Programming The Go Parallel Website, sponsored
by Intel and developed in partnership with Slashdot Media, is your hub for all
things parallel software development, from weekly thought leadership blogs to
news, videos, case studies, tutorials and more. Take a look and join the
conversation now. http://goparallel.sourceforge.net/
_______________________________________________
Mspgcc-users mailing list
[hidden email]
https://lists.sourceforge.net/lists/listinfo/mspgcc-users
Loading...