If really you want to use gcc-style inline assembly you really need a later
compiler.
Or, if you are backporting to an older environment -- you will have to
re-write those pieces in regular assembly (.s files) or to use sun-style
inline assembly (.il files). You can read about .il files in thi
Joerg,
This is now CR:6872875.
Alexander
On Thu, 13 Aug 2009, Joerg Schilling wrote:
> Since a longer time, the SunStudio optimizer creates significantly
> better optimized code for intel 32 Bit binaries (typically 20%-30%
> faster than what GCC creates).
>
> If you try to create 64 bit binari
On Mon, 17 Aug 2009, Chris Quenelle wrote:
>
> An easy check would be to see if there is a Makefile
> glitch of some kind, and you're getting some 32-bit
> binaries when you think you're getting 64-bit binaries.
> That would run significantly slower on x86.
>
> Something like: find . -type f | xa
On Tue, 16 Jun 2009, James Carlson wrote:
> Alexander.Gorshenev at Sun.COM writes:
>> So is it something to be addressed later or users just have to live
>> with it from now on?
>
> The 'hg keywords' check will tell you to remove that old SCCS-based
> swill when you're updating files. The general
The /usr/include headers in Solaris used to have #pragma ident lines
such as
#pragma ident "@(#)strings.h 1.3 96/03/12 SMI.
Sun Studio compilers put such lines from standard headers (as well as
other files) to the binary files. So that one can
$mcs -p hello.o
hello.o:
@(#)stdio.h 1.
No, we don't. It was requested though and can appear in a next release. The
bugid is 6566285.
On Fri, 17 Apr 2009, Christian Thalinger wrote:
> Hi!
>
> Does Sun Studio have something like an inlining depth limit? And if
> yes, what is it's value and can it be tuned?
>
> -- Christian
>
> __
On Wed, 25 Feb 2009, Chris Ridd wrote:
>
> On 24 Feb 2009, at 20:23, C. Bergstr?m wrote:
>
>>
>> Since the xorg driver size issue I've been looking at the objdump of some
>> binaries and the code generation between sun cc, gcc and open64..
>>
>> CSiBE gave some interesting rough size comparison
I took a look only at tst0.f90, but I think that the inswer is RTFM.
man -s 3f rand
suggests that it is important to specify a proper numerical value to the rand()
function.
Alexander
On Mon, 16 Jun 2008, Reginald Beardsley wrote:
> Alexander,
>
> Attached is a gzipped tarball w/ a makefile
Could you please be a little be more specific. Can you reduce your
problem to a reproducible test case and also tell us the exact command
line you use for compilation and the platform you compile for?
There can be numerous reasons for a call not being executed. For example
it can be in a "dead"
On Mon, 9 Jun 2008, Roland Mainz wrote:
> Kuldip Oberoi wrote:
>> Roland Mainz wrote:
>>> Sean Sprague wrote:
> Does anyone know when (approximately) the Sun Studio version after
> "Studio 12" will be released ?
>
I guess that the obvious question is "what extraq functionality do
On Wed, 19 Mar 2008, Roland Mainz wrote:
> Keith M Wesolowski wrote:
>> On Sat, Mar 15, 2008 at 04:47:25PM +0100, Roland Mainz wrote:
>
>> One example
>> I can think of that will sneak past is something like:
>>
>> foo.c:
>> int
>> foo(int *x)
>> {
>> return (0);
>> }
>>
>> bar.c:
>> exter
On Mon, 17 Mar 2008, Roland Mainz wrote:
> Keith M Wesolowski wrote:
>> On Sat, Mar 15, 2008 at 04:47:25PM +0100, Roland Mainz wrote:
>>> Does anyone know tools to track down problems caused by uninitalised
>>> global or stack variables except dbx's "check -access" functionality
>>> (which doesn't
On Fri, 21 Dec 2007, Roland Mainz wrote:
>
> Hi!
>
>
>
> Does Sun Studio/Forte/Workshop have an option to sort functions+data
> automagically that related functions+read-only data are kept close
> together, maybe share the same memory page (the idea would be to reduce
> the number of ITLB+DTL
13 matches
Mail list logo
