aboutsummaryrefslogtreecommitdiff
path: root/libatomic
diff options
context:
space:
mode:
authorAldy Hernandez <aldyh@redhat.com>2021-04-19 08:24:11 +0200
committerAldy Hernandez <aldyh@redhat.com>2021-05-01 09:28:33 +0200
commit3c65858787dc52b65b26fa7018587c01510f442c (patch)
treec41a7763618c9c97b881b87ad6688b0ac51af83d /libatomic
parent69c426b89579312af91035c26fb1e270bfbcad00 (diff)
downloadgcc-3c65858787dc52b65b26fa7018587c01510f442c.zip
gcc-3c65858787dc52b65b26fa7018587c01510f442c.tar.gz
gcc-3c65858787dc52b65b26fa7018587c01510f442c.tar.bz2
Add GTY support for irange.
Right now we have GTY support for static storage iranges (int_range<>). However, there's no reason why the base class can't be used with GC, other than it was an oversight. For that matter, the base class has a pointer to the sub-range storage, so we can use the same implementation for both. This patch does so. I have also removed the DEFINE_INT_RANGE_GC_STUBS stuff, and have documented why we need a separate gt_pch_nx (int_range<1> *&) version. This has to do with hash-traits.h, which ipa-prop.c is using to store a value_range. The header file hash-traits.h is defining an extern of gt_pch_nx (int_range<1> *&) etc, instead of calling the more generic (int_range<1> *) which is already available. It seems suspect that has-traits.h has their own externs for GC functions, and if someone has a better solution, I'd be glad to hear it. gcc/ChangeLog: * value-range.cc (DEFINE_INT_RANGE_GC_STUBS): Remove. (gt_pch_nx (int_range<1> *&)): New. (gt_ggc_mx (int_range<1> *&)): New. * value-range.h (class irange): Add GTY support for the base class.
Diffstat (limited to 'libatomic')
0 files changed, 0 insertions, 0 deletions