- Community Home
- >
- Servers and Operating Systems
- >
- Operating Systems
- >
- Operating System - Linux
- >
- Re: aCC version and ANSI compliance
Categories
Company
Local Language
Forums
Discussions
Forums
- Data Protection and Retention
- Entry Storage Systems
- Legacy
- Midrange and Enterprise Storage
- Storage Networking
- HPE Nimble Storage
Discussions
Discussions
Discussions
Forums
Forums
Discussions
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
- BladeSystem Infrastructure and Application Solutions
- Appliance Servers
- Alpha Servers
- BackOffice Products
- Internet Products
- HPE 9000 and HPE e3000 Servers
- Networking
- Netservers
- Secure OS Software for Linux
- Server Management (Insight Manager 7)
- Windows Server 2003
- Operating System - Tru64 Unix
- ProLiant Deployment and Provisioning
- Linux-Based Community / Regional
- Microsoft System Center Integration
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Community
Resources
Forums
Blogs
- Subscribe to RSS Feed
- Mark Topic as New
- Mark Topic as Read
- Float this Topic for Current User
- Bookmark
- Subscribe
- Printer Friendly Page
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО08-16-2006 01:30 AM
тАО08-16-2006 01:30 AM
aCC version and ANSI compliance
I wish to know what the above compiler version means (I am using hpux11.11 9000/800 PA_RISK Version 2.)
In a more general mode: what is the level of compliance of differnt compiler versions with the ANSI standard.
Thanks
David
- Tags:
- maxssiz
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО08-16-2006 02:00 AM
тАО08-16-2006 02:00 AM
Re: aCC version and ANSI compliance
First, the kernel tunable maxssiz (and if a 64-bit executable maxssiz_64bit) this defaults to 8MiB and only VERY poorly written code would ever require a stack larger than 64MiB and I generally set it to 32MiB for both 32-bit and 64-bit executables. The second limit is ulimit -s value.
You can find your current stack size by "ulimit -s".
For your last question, I would say read the documentation.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО08-16-2006 07:47 AM
тАО08-16-2006 07:47 AM
Re: aCC version and ANSI compliance
As Clay mentioned, the size is limited by maxssiz. Unless you are using threads.
Instead of using strings, you may want to use
char *p= new char[5001];
Of course you need to delete before returning.
A.03.50 is 3 years old and the latest version is A.03.70. A reference to the C++ Standards is on:
http://www.docs.hp.com/en/7762/5991-4874/standards.htm#stdunsup
>Clay: The stack size has nothing to do with the compiler.
While the compiler doesn't control the total size, the compiler can create giant frames by excessive inlining. And in a threaded environment, the stack is limited to 64 Kb default.
- Tags:
- stack overflow
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО08-16-2006 08:05 AM
тАО08-16-2006 08:05 AM
Re: aCC version and ANSI compliance
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО08-16-2006 02:33 PM - edited тАО10-30-2011 08:20 PM
тАО08-16-2006 02:33 PM - edited тАО10-30-2011 08:20 PM
Re: aCC version and ANSI compliance
>Clay: so long as the total of all this does not exceed maxssiz.
The thread stacks are allocated in the heap or mmaps, so maxssiz has nothing to do with them.