Hi,
This is a limitation of cudnn that does not implement it.
You can disable cudnn during the forward computation of that RNN if you want to be able to do that by falling back to our own implementation that does support it
with torch.backends.cudnn.flag(enabled=False):
    # Your rnn forward code