Skip to content

Conversation

@laidene
Copy link
Contributor

@laidene laidene commented Dec 15, 2025

… in a for loop

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

[

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

避免在循环内重复计算 shstrab。Redundant calculations in a for loop.

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

移到循环外部,只计算一次。Move outside the loop to calculate only once.

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

请提供验证的bsp和config (provide the config and bsp)
BSP: bsp/qemu-vexpress-a9
.config: 无
action: 无

]

当前拉取/合并请求的状态 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自查

@laidene laidene requested a review from mysterywolf as a code owner December 15, 2025 06:11
@github-actions
Copy link

👋 感谢您对 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:opt/components/libc/libdl
  • 设置PR number为 \ Set the PR number to:11062
  1. 等待工作流完成 | Wait for the workflow to complete
    格式化后的代码将自动推送至你的分支。
    The formatted code will be automatically pushed to your branch.

完成后,提交将自动更新至 opt/components/libc/libdl 分支,关联的 Pull Request 也会同步更新。
Once completed, commits will be pushed to the opt/components/libc/libdl 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 Dec 15, 2025

📌 Code Review Assignment

🏷️ Tag: components

Reviewers: Maihuanyi

Changed Files (Click to expand)
  • components/libc/posix/libdl/dlelf.c

🏷️ Tag: components_libc

Reviewers: GorrayLi mysterywolf

Changed Files (Click to expand)
  • components/libc/posix/libdl/dlelf.c

📊 Current Review Status (Last Updated: 2025-12-15 16:10 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.

@CLAassistant
Copy link

CLAassistant commented Dec 15, 2025

CLA assistant check
All committers have signed the CLA.

@laidene laidene force-pushed the opt/components/libc/libdl branch from b75d355 to cbef04a Compare December 15, 2025 08:09
@Rbb666
Copy link
Member

Rbb666 commented Dec 17, 2025

请作者签署下CLA,然后给出测试截图

@laidene
Copy link
Contributor Author

laidene commented Dec 18, 2025

测试记录

在 qemu-vexpress-a9 中打开 CONFIG_RT_USING_MODULE,测试程序和截图。

创建一个动态库程序

#ifndef __ADD_H__
#define __ADD_H__

#ifdef __cplusplus
extern "C" {
#endif

/**
 * 加法函数
 * @param a 第一个加数
 * @param b 第二个加数
 * @return 返回 a + b 的结果
 */
int add(int a, int b);

#ifdef __cplusplus
}
#endif

#endif /* __ADD_H__ */
#include "add.h"

#include <rtthread.h>

/**
 * 加法函数实现
 * @param a 第一个加数
 * @param b 第二个加数
 * @return 返回 a + b 的结果
 */
int add(int a, int b)
{   
    rt_kprintf("add: %d + %d = %d\n", a, b, a + b);
    return a + b;
}

调用动态库测试程序

/**
 * 测试动态库加载和调用的示例程序
 * 需要在RT-Thread中启用动态模块加载功能
 */

#include <rtthread.h>
#include <dlfcn.h>
#include <stdio.h>

#ifdef RT_USING_MODULE

/* 动态库路径 */
#define LIBADD_PATH "/lib/libadd.so"

/* 函数指针类型定义 */
typedef int (*add_func_t)(int a, int b);

static void test_add_lib(void)
{
    void *handle;
    add_func_t add_func;
    int result;
    const char *error;

    rt_kprintf("Testing dynamic library: %s\n", LIBADD_PATH);

    /* 打开动态库 */
    handle = dlopen(LIBADD_PATH, RTLD_LAZY);
    if (!handle) {
        rt_kprintf("Error: Cannot open library %s: %s\n", LIBADD_PATH, dlerror());
        return;
    }

    rt_kprintf("Library opened successfully\n");

    /* 获取add函数地址 */
    add_func = (add_func_t)dlsym(handle, "add");

    rt_kprintf("Symbol 'add' found successfully\n");

    /* 调用add函数 */
    result = add_func(10, 20);
    rt_kprintf("[c] add(10, 20) = %d\n", result);

    result = add_func(100, 200);
    rt_kprintf("[c] add(100, 200) = %d\n", result);

    result = add_func(-5, 15);
    rt_kprintf("[c] add(-5, 15) = %d\n", result);

    /* 关闭动态库 */
    dlclose(handle);
    rt_kprintf("Library closed\n");
}
MSH_CMD_EXPORT(test_add_lib, Test dynamic library add function);

#else
    #warning "RT_USING_MODULE is not defined, please enable dynamic module loading in Kconfig"
#endif /* RT_USING_MODULE */

运行截图

image

@laidene
Copy link
Contributor Author

laidene commented Dec 18, 2025

请作者签署下CLA,然后给出测试截图

我已经签署并添加测试截图评论

@Rbb666 Rbb666 merged commit d09135f into RT-Thread:master Dec 18, 2025
61 of 88 checks passed
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.

3 participants