|
Bugzilla – Full Text Bug Listing |
| Summary: | uint128_t type not portable | ||
|---|---|---|---|
| Product: | ns-3 | Reporter: | Tom Henderson <tomh> |
| Component: | internet | Assignee: | Tommaso Pecorella <tommaso.pecorella> |
| Status: | RESOLVED FIXED | ||
| Severity: | normal | CC: | ns-bugs |
| Priority: | P3 | ||
| Version: | unspecified | ||
| Hardware: | All | ||
| OS: | All | ||
|
Description
Tom Henderson
2018-02-08 11:29:51 UTC
Not a big issue. I can use two uint64_t there. However... what should we do with all the other places where uint128_t is used ? Should we deprecate it ? T. (In reply to Tommaso Pecorella from comment #1) > Not a big issue. I can use two uint64_t there. > > However... what should we do with all the other places where uint128_t is > used ? > Should we deprecate it ? > > T. My scan of the codebase is that it is only used in the int64x64 code in core, but multiple implementations with a fallback if uint128_t is not available on the platform. So I think we need to just fix it in the newly committed code. fixed in changeset: 13281:fcb5d90f5a27 |