-
Notifications
You must be signed in to change notification settings - Fork 76
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
call of overloaded 'softdouble(int)' is ambiguous #11
Comments
Looks like there was a related change in the esp-2022r1-RC1 release:
I think that means that Will test this shortly EDIT: this also seems relevant: ESP-IDF Programming Guide migration to 5.0 |
I'm getting new errors, so I guess that's progress :) I'm going to go and chip away at these to see if I can get it compiling with the latest toolchain |
Hello, did you solve it or made more progress @R3volv360 ? It would really help me. |
@jcandel01 unfortunately not. A combination of personal issues and my general lack of deep C++ understanding hindered me enough to put it down for now. I do have an ESP32 chip now just sitting around doing nothing, so maybe when I have more time I'll pick this up again, but no significant progress unfortunately. |
Hey, I think I found a solution to this. Please create a file with the below content in it
and add the below flag to your compiler C++ flag variable
ultimately your CMAKE_CXX_FLAG command should look something like as shown below
|
I downgraded the toolchain to esp-2021r2-patch3 . This eliminated the softdouble(int) issue, and the default esp32 build finished. |
I'm seeing the following error on
make
that isn't referenced in the docs:Further up in the code it has:
#define EXPTAB_SCALE 6
so the complaint seems to be aboutfloat64_t(1 << EXPTAB_SCALE)
=float64_t(1 << 6)
=float64_t(64)
?The definitions all refer to
[u]int[size]_t
and none forint
. I am building this with thextensa-esp32-elf/esp-2022r1-11.2.0/xtensa-esp32-elf/bin/xtensa-esp32-elf-g++
compiler. The docs show that it usedxtensa-esp32-elf/esp-2019r2-8.2.0/xtensa-esp32-elf/bin/xtensa-esp32-elf-g++
(the difference beingesp-2022r1-11.2.0
vsesp-2019r2-8.2.0
).I don't have the C++ knowledge to formulate a good guess on why this isn't working with the ESP32 build setup vs compiling it for my 64bit Ubuntu machine. Why would the call not be ambiguous in the latter case, but with the ESP32 build it can't decide which method to use?
If I did have to guess I would think there is some difference in how integer types are being handled in the
xtensa-esp32-elf/esp-2019r2-8.2.0
compiler vs thextensa-esp32-elf/esp-2022r1-11.2.0
, but I also have no idea how to check that.The text was updated successfully, but these errors were encountered: