blocks|key|2571960|text|这是一个有点粗略的-+HW架构，内存模型等都会影响C/C%2B%2B实现可能具有“段”特性的方式。旧的CPU有局限性，导致了一组更复杂的“段”(iAPX+286+-还记得吗？)所以把这当作一个粗俗的介绍，谷歌的热门词，.|type|unstyled|depth|inlineStyleRanges|entityRanges|data|2571961|对象代码包含可执行语句产生的代码:由组装的机器指令产生的字节。这将进入代码段，这将(通常)导致一个受写保护的内存段。|2571962|对象代码包含数据:由组装的数据定义语句产生的字节，在某些初始化(或默认情况下为零，在C/C%2B%2B情况下)，这将进入数据段，不受访问限制。|2571963|CPU的工作方式需要一个堆栈:在堆栈上推送返回地址，并通过推送函数参数传递最有效的参数约定。“堆栈帧”部分是“按约定”，但通常由返回地址和参数组成；为局部变量保留额外的空间:为每个实例化保留一组(如果函数是递归的，这很重要)。|2571964|堆只是一个内存区域，分配(malloc，new)是从该区域提供的。它通常被分配到代码和数据段之外。堆栈可以从堆中取出--这里取决于您是只有一个堆栈段还是几个堆栈段(比如线程)。|2571965|此外，请注意，有几种对象代码“格式”或“语言”，即如何在对象代码中定义这些段。这取决于系统的加载程序能够处理什么:一种这样的格式称为"a.out"，另一种是"ELF“。编译器必须遵守格式和可能性。|2571966|entityMap^0|0|0|0|0|0|0^^$0|@$1|2|3|4|5|6|7|N|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|O|8|@]|9|@]|A|$]]|$1|D|3|E|5|6|7|P|8|@]|9|@]|A|$]]|$1|F|3|G|5|6|7|Q|8|@]|9|@]|A|$]]|$1|H|3|I|5|6|7|R|8|@]|9|@]|A|$]]|$1|J|3|K|5|6|7|S|8|@]|9|@]|A|$]]|$1|L|3|-4|5|6|7|T|8|@]|9|@]|A|$]]]|M|$]]

This is a little sketchy - HW architectures, memory models etc. all influence the way a C/C++ implementation may feature "segments". Older CPUs had limitations, resulting in a more complicated set of "segments" (iAPX 286 - remember?) So just take this as a crude intro, google for the buzz words,...

Object code contains code resulting from executable statements: bytes resulting from the assembled machine instructions. This will go into a code segement, which will (typically) result in a memory segment that is write protected.

Object code contains data: bytes resulting from assembled data definition statements, with some initialization (or default, zero in case of C/C++), This will go into a data segment, without access restrictions.

A stack is required by the way your CPU works: pushing a return address on the stack, with the most efficient convention of parameter passing by pushing function parameters as well. A "stack frame" is partly "by convention", but typically it consists of the return address and parameters; additional space is reserved for local variables: one set for each instantiation (which is important if the function is recursive).

The heap is just a memory area from which allocations (malloc, new) are being served. It is typically allocated beyond code and data segments. Stacks may be taken out of the heap - here it depends whether you have just a single stack segment or several (think threads).

Additionally, note that there are several object code "formats" or "languages", i.e., ways how these segments are being defined in the object code. This depends on what a system's loader can handle: one such format is known as "a.out", another one is "ELF". Compilers must adhere to the format and possibilities.

blocks|key|2180110|text|它们是由c/c%2B%2B编译器程序员在编写语言实现时编写的吗？或者这些段是在OS+/硬件级别实现的(可能是当OS为程序选择一个地址空间时)？
|type|blockquote|depth|inlineStyleRanges|entityRanges|data|2180111|unstyled|2180112|段入口点主要在工具链的链接阶段(和链接器程序)进行管理。|2180113|从这个意义上说，是的，这些是由编译器开发人员实现的。|2180114|不过，您可以提供自己的链接器脚本，您可以在其中指定应该在哪些具体内存地址中发生这些段，以及这些内存地址是否指ROM或RAM。|2180115|我把堆栈框架想象成一个简单的c%2B%2B结构，它被推入堆栈中，用于每个函数调用。我把堆想象成一个动态数组等等.
|2180116|2180117|恐怕没有那么简单：|2180118|堆栈框架通常还需要跟踪本地实例化变量、堆栈异常展开所需的信息等。|unordered-list-item|2180119|堆分配的内存需要一些基本机制来跟踪分配的内存块及其实际大小。|2180120|静态内存初始化和类初始化需要运行静态实例类的构造函数。|2180121|2180122|2180123|entityMap^0|0|0|0|0|0|0|0|0|0|0|0|0|0^^$0|@$1|2|3|4|5|6|7|Z|8|@]|9|@]|A|$]]|$1|B|3|-4|5|C|7|10|8|@]|9|@]|A|$]]|$1|D|3|E|5|C|7|11|8|@]|9|@]|A|$]]|$1|F|3|G|5|C|7|12|8|@]|9|@]|A|$]]|$1|H|3|I|5|C|7|13|8|@]|9|@]|A|$]]|$1|J|3|K|5|6|7|14|8|@]|9|@]|A|$]]|$1|L|3|-4|5|C|7|15|8|@]|9|@]|A|$]]|$1|M|3|N|5|C|7|16|8|@]|9|@]|A|$]]|$1|O|3|P|5|Q|7|17|8|@]|9|@]|A|$]]|$1|R|3|S|5|Q|7|18|8|@]|9|@]|A|$]]|$1|T|3|U|5|Q|7|19|8|@]|9|@]|A|$]]|$1|V|3|-4|5|C|7|1A|8|@]|9|@]|A|$]]|$1|W|3|-4|5|C|7|1B|8|@]|9|@]|A|$]]|$1|X|3|-4|5|C|7|1C|8|@]|9|@]|A|$]]]|Y|$]]

<blockquote>
 Are they written by the c/c++ compiler programmers when they write the implementation of the language? Or are these segments implemented at the OS/hardware level(maybe when the OS chooses an address space for a program)?
</blockquote>

The segment entry points are primarily managed at the linking stage (and the linker program) of the toolchain. 

In that sense, Yes these are implemented by the compiler developers. 

You can provide your own linker script though, where you can specify at which concrete memory addresses these segments should occur, and if these memory addresses refer to ROM or RAM.

<blockquote>
 I imagine a stack frame as a simple c struct which is pushed into the stack for every function call. I imagine the heap as a dynamic array and so on...
</blockquote>

It's at all not that simple I'm afraid:

<ul>
<li>The stack frame usually also needs to keep track about the locally instantiated variables, the information necessary for stack unwinding on exceptions, etc.</li>
<li>The heap allocated memory needs some basic mechanism to keep track of the allocated memory blocks and their actual size.</li>
<li>The static memory initialization and class initialization needs to run the constructors of statically instatiated classes.</li>
</ul>

I know the purpose of every segment, but I was wondering who actually implements them in languages such as c or c++?

Are they written by the c/c++ compiler programmers when they write the implementation of the language? Or are these segments implemented at the OS/hardware level(maybe when the OS chooses an address space for a program)?

I imagine a stack frame as a simple c struct which is pushed into the stack for every function call. I imagine the heap as a dynamic array and so on...

Code, static, stack and heap segments implementation

翻译质量差，导致语言生硬或混乱。

没有提供实际的解决方法或示例。

解答不清晰，无法理解或解决问题。

页面排版不美观，阅读体验差。

文章

问答

视频

学习中心

腾讯云实验室

直播

竞赛

腾讯云代码分析专区

腾讯iOA零信任安全管理系统专区

腾讯云架构师技术同盟交流圈

腾讯云数据库专区

腾讯云顾问专区

腾讯云原生专区

腾讯混元专区

腾讯云TCE专区

腾讯云Lighthouse专区

腾讯云HAI专区

腾讯云Edgeone专区

腾讯云存储专区

腾讯云智能专区

腾讯轻联专区 

腾讯云开发专区

TAPD专区

腾讯轻量云游戏服专区

腾讯云最具价值专家

腾讯云架构师技术同盟

腾讯云创作之星

腾讯云开发者先锋

腾讯云代码助手

云原生构建

TAPD 敏捷项目管理

Cloud Studio

SDK中心

API中心

命令行工具

涵盖代码开发、场景应用、自动测试全流程，助你从零构建专属AI助手

一站式MCP教程库，解锁AI应用新玩法

我知道每个片段的用途，但我想知道是谁用c或c++这样的语言实现它们呢？它们是由c/c++编译器程序员在编写语言实现时编写的吗？或者这些段是在OS /硬件级别实现的(可能是当OS为程序选择一个地址空间时)？我把堆栈框架想象成一个简单的c++结构，它被推入堆栈中，用于每个函数调用。我把堆想象成一个动态数组等等.

问代码、静态、堆栈和堆段实现
EN

Stack Overflow用户

社区

活动

圈层

关于

腾讯云开发者

热门产品

热门推荐

更多推荐

问代码、静态、堆栈和堆段实现EN