Skip to content

Bug fixes and link-time-optimization support for GCC 12
Compare
Choose a tag to compare
@wravery wravery released this 24 May 20:14
· 108 commits to main since this release
v4.5.0
8c1623a
This commit was created on GitHub.com and signed with GitHub’s verified signature. The key has expired.
GPG key ID: 4AEE18F83AFDEB23
Expired
Verified
Learn about vigilant mode.

The most notable change was part of the fix for #254 in #256. In the course of debugging it, I realized that response::IdType was being overly aggressive about trying to interpret any string that was a valid Base64 encoding as a Base64 encoded vector of bytes:

I'm bumping the minor version because response::IdType in inputs/arguments is going to be a string all the time internally, and that changes which accessors you can use on field arguments. It's generally more consistent now, but if you are used to using it with Base64 encoded binaries and your code assumes that's what it contains, you may need to perform the conversion explicitly with argId.release<response::IdType::ByteData>() rather than using the const ByteData accessors. You can still use response::IdType::isBase64() to tell if it's safe to release it as a binary (otherwise it will throw an exception for strings which are not valid Base64 encodings), and it's always safe to release it as a string. It's also always safe to use the const c_str() OpaqueString accessor on response::IdType field arguments now because they are guaranteed to hold a string internally.

The response::IdType::ByteData type is just an alias for std::vector<std::uint8_t>, which was the original type for response::IdType before I added std::string support, so you could also write the release call as argId.release<std::vector<std::uint8_t>>() if that looks better to you. The same applies to response::IdType::OpaqueString vs. std::string.

Otherwise, most of the changes since v4.4.1 have to do with fixing warnings and errors that showed up when enabling LTO (link-time-optimization) in GCC 10 and 12. The project, including all samples and tests, should now build cleanly with GCC using the -flto=auto compiler flag.

What's Changed

  • Update PEGTL version number in README by @wravery in #253
  • Fix source lifetime and preserve input strings in response::IdType by @wravery in #256
  • Miscellaneous warnings and errors which showed up in GCC 12 by @wravery in #257
  • Adding Microsoft SECURITY.MD by @microsoft-github-policy-service in #259
  • Cleanup redundant inline specifiers by @wravery in #262

New Contributors

  • @microsoft-github-policy-service made their first contribution in #259

Full Changelog: v4.4.1...v4.5.0

Contributors

wravery
Assets 2
Loading