Thanks to visit codestin.com
Credit goes to github.com

Skip to content

Conversation

@ChengyangMa
Copy link

…functions

拉取/合并请求描述:(PR description)

[

为什么提交这份PR (why to submit this PR)

执行新手PR任务,为LIBC文件夹下的libc函数提供注释

你的解决方案是什么 (what is your solution)

查询mircosoft c++英文手册和询问deepseek,给 components/libc/compilers/armlibc/syscall_mem.c 中的所有libc函数编写了英文注释

请提供验证的bsp和config (provide the config and bsp)

由于是撰写注释,所以我没有进行验证

]

当前拉取/合并请求的状态 Intent for your PR

必须选择一项 Choose one (Mandatory):

  • 本拉取/合并请求是一个草稿版本 This PR is for a code-review and is intended to get feedback
  • [*] 本拉取/合并请求是一个成熟版本 This PR is mature, and ready to be integrated into the repo

代码质量 Code Quality:

我在这个拉取/合并请求中已经考虑了 As part of this pull request, I've considered the following:

  • [*] 已经仔细查看过代码改动的对比 Already check the difference between PR and old code
  • [*] 代码风格正确,包括缩进空格,命名及其他风格 Style guide is adhered to, including spacing, naming and other styles
  • [*] 没有垃圾代码,代码尽量精简,不包含#if 0代码,不包含已经被注释了的代码 All redundant code is removed and cleaned up
  • [*] 所有变更均有原因及合理的,并且不会影响到其他软件组件代码或BSP All modifications are justified and not affect other components or BSP
  • [*] 对难懂代码均提供对应的注释 I've commented appropriately where code is tricky
  • [*] 代码是高质量的 Code in this PR is of high quality
  • [*] 已经使用formatting 等源码格式化工具确保格式符合RT-Thread代码规范 This PR complies with RT-Thread code specification
  • [*] 如果是新增bsp, 已经添加ci检查到.github/ALL_BSP_COMPILE.json 详细请参考链接BSP自查

@CLAassistant
Copy link

CLAassistant commented Nov 1, 2025

CLA assistant check
All committers have signed the CLA.

@github-actions
Copy link

github-actions bot commented Nov 1, 2025

👋 感谢您对 RT-Thread 的贡献!Thank you for your contribution to RT-Thread!

为确保代码符合 RT-Thread 的编码规范,请在你的仓库中执行以下步骤运行代码格式化工作流(如果格式化CI运行失败)。
To ensure your code complies with RT-Thread's coding style, please run the code formatting workflow by following the steps below (If the formatting of CI fails to run).


🛠 操作步骤 | Steps

  1. 前往 Actions 页面 | Go to the Actions page
    点击进入工作流 → | Click to open workflow →

  2. 点击 Run workflow | Click Run workflow

  • 设置需排除的文件/目录(目录请以"/"结尾)
    Set files/directories to exclude (directories should end with "/")
  • 将目标分支设置为 \ Set the target branch to:test1
  • 设置PR number为 \ Set the PR number to:10880
  1. 等待工作流完成 | Wait for the workflow to complete
    格式化后的代码将自动推送至你的分支。
    The formatted code will be automatically pushed to your branch.

完成后,提交将自动更新至 test1 分支,关联的 Pull Request 也会同步更新。
Once completed, commits will be pushed to the test1 branch automatically, and the related Pull Request will be updated.

如有问题欢迎联系我们,再次感谢您的贡献!💐
If you have any questions, feel free to reach out. Thanks again for your contribution!

@github-actions
Copy link

github-actions bot commented Nov 1, 2025

📌 Code Review Assignment

🏷️ Tag: components

Reviewers: Maihuanyi

Changed Files (Click to expand)
  • components/libc/compilers/armlibc/syscall_mem.c

🏷️ Tag: components_libc

Reviewers: GorrayLi mysterywolf

Changed Files (Click to expand)
  • components/libc/compilers/armlibc/syscall_mem.c

📊 Current Review Status (Last Updated: 2025-11-03 16:59 CST)

  • GorrayLi Pending Review
  • Maihuanyi Pending Review
  • mysterywolf Pending Review

📝 Review Instructions

  1. 维护者可以通过单击此处来刷新审查状态: 🔄 刷新状态
    Maintainers can refresh the review status by clicking here: 🔄 Refresh Status

  2. 确认审核通过后评论 LGTM/lgtm
    Comment LGTM/lgtm after confirming approval

  3. PR合并前需至少一位维护者确认
    PR must be confirmed by at least one maintainer before merging

ℹ️ 刷新CI状态操作需要具备仓库写入权限。
ℹ️ Refresh CI status operation requires repository Write permission.

@Rbb666 Rbb666 requested a review from unicornx November 2, 2025 09:23
@supperthomas supperthomas requested a review from Copilot November 3, 2025 01:34
Copy link
Contributor

Copilot AI left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Pull Request Overview

This PR adds comprehensive documentation comments for memory management wrapper functions (malloc, realloc, calloc, free) in the ARM compiler libc implementation. The changes improve code documentation by adding detailed function descriptions, parameter explanations, and return value documentation in Doxygen format.

Key Changes

  • Added detailed Doxygen-style comments for all four memory allocation/deallocation functions
  • Documented parameters, return values, and special behavior when heap is not configured
  • Updated the file change log to reflect the documentation additions

* Date Author Notes
* 2014-08-03 bernard Add file header
* 2021-11-13 Meco Man implement no-heap warning
* 2025-11-1 MaChengyang Add detailed function comments
Copy link

Copilot AI Nov 3, 2025

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Date format is inconsistent with other entries. Should use 'YYYY-MM-DD' format (2025-11-01) instead of 'YYYY-MM-D' (2025-11-1). / 日期格式与其他条目不一致。应使用 'YYYY-MM-DD' 格式(2025-11-01)而不是 'YYYY-MM-D'(2025-11-1)。

Suggested change
* 2025-11-1 MaChengyang Add detailed function comments
* 2025-11-01 MaChengyang Add detailed function comments

Copilot uses AI. Check for mistakes.
* Date Author Notes
* 2014-08-03 bernard Add file header
* 2021-11-13 Meco Man implement no-heap warning
* 2025-11-1 MaChengyang Add detailed function comments
Copy link

Copilot AI Nov 3, 2025

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Trailing whitespace detected at the end of the line. Remove the extra spaces after 'comments'. / 检测到行尾有多余的空格。请删除 'comments' 之后的空格。

Suggested change
* 2025-11-1 MaChengyang Add detailed function comments
* 2025-11-1 MaChengyang Add detailed function comments

Copilot uses AI. Check for mistakes.
#endif /* __CC_ARM */

/**
* @brief Allocate memory block
Copy link

Copilot AI Nov 3, 2025

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

There are two spaces between '@brief' and the description. According to Doxygen conventions, only one space should be used. This inconsistency appears in all added function comments (lines 32, 59, 94, 122). / '@brief' 和描述之间有两个空格。根据 Doxygen 惯例,应该只使用一个空格。这个不一致出现在所有添加的函数注释中(第 32、59、94、122 行)。

Copilot uses AI. Check for mistakes.
@kurisaW kurisaW closed this Nov 3, 2025
@kurisaW kurisaW reopened this Nov 3, 2025
* Date Author Notes
* 2014-08-03 bernard Add file header
* 2021-11-13 Meco Man implement no-heap warning
* 2025-11-1 MaChengyang Add detailed function comments
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

建议不要更新这种列表了,不理解为啥 RTT 还在用这种很古老的方式。现在有 git,在git 的 commit 里加上你的签名就好了,可以看一下其他用 git的开源项目里的加签名的方式 ”Signed-off-by: Your name "。

*
* @note The returned pointer is always suitably aligned for any built-in type.
* @see rt_malloc
*/
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

建议仔细看一下 https://rt-thread.github.io/rt-thread/page_howto_function.html 了解如何为函数写 doxygen 注释。

另外,对于 “@see” 如果是指向函数,建议写成 “@see rt_malloc()”

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Projects

None yet

Development

Successfully merging this pull request may close these issues.

4 participants